Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refinery 1.6.0 Docker image fails to start without arguments #350

Closed
martinmcnulty opened this issue Nov 10, 2021 · 3 comments · Fixed by #352
Closed

Refinery 1.6.0 Docker image fails to start without arguments #350

martinmcnulty opened this issue Nov 10, 2021 · 3 comments · Fixed by #352
Assignees
Labels
type: bug Something isn't working

Comments

@martinmcnulty
Copy link

Versions

  • Refinery: 1.6.0 (Docker image)

Steps to reproduce

  1. Create refinery.toml and rules.toml in a subdir called conf
  2. Run docker run -v $(pwd)/conf:/etc/refinery honeycombio/refinery:1.6.0
  3. The container exits immediately with an error message:
$ ls conf/
refinery.toml  rules.toml
$ docker run -v $(pwd)/conf:/etc/refinery honeycombio/refinery:1.6.0
command line parsing error - call with --help for usage
$

Additional context

In 1.5.2, the container started with no arguments:

$ docker run -v $(pwd)/conf:/etc/refinery honeycombio/refinery:1.5.2
time="2021-11-10T15:45:45Z" level=info msg="using specific identifier from config" identifier=192.168.1.1
time="2021-11-10T15:45:46Z" level=info msg="Peer list has changed. New peer list: [http://10.40.192.136:28957 http://10.40.192.139:22052 http://192.168.1.1:12346]"
...
@JamieDanielson
Copy link
Contributor

Thank you for reporting @martinmcnulty! We'll get this fixed up.

@MikeGoldsmith
Copy link
Contributor

Hey @martinmcnulty - we released v1.6.1 with a fix. Let us know if you have any more issues.

@martinmcnulty
Copy link
Author

Looks good! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants