-
Notifications
You must be signed in to change notification settings - Fork 20
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
Run clock-bound-d on Docker #8
Comments
Hi, Can work on adding the configuration option for the port, should be simple enough. As for the syslog, I don't see why syslog won't be working on the docker. Would you be able to verify if syslog is installed and running on your Docker? |
I'll work on it (I'm not familiar with Rust, so it will take some time).
Syslog is not installed and not running in my Docker image. |
Open to patches to add support for stdout/stderr, theres no hard dependency on syslog. |
Hello.
I would like to run clock-bound-d on Docker, but there are probably two barriers.
I wrote the following Dockerfile, but this gives me an error.
When running clock-bound-d on Docker, I'm thinking of running chrony as a side car.
For example, I'm thinking of using https://github.com/cturra/docker-ntp , which works with port 123.
I think a workaround is possible, but it would be useful to be able to use a port other than 323.
Are there any plans to make these two points configurable?
The text was updated successfully, but these errors were encountered: