-
Notifications
You must be signed in to change notification settings - Fork 554
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
moby-engine package should not include /etc/docker/daemon.json #8961
Comments
For this specific binary, upstream does not seem to try to resolve it from libexec. It may be reasonable to look for |
Thanks for the report @paulmey! I'm looking into the appropriate fix here and will prioritize making sure that /etc/docker/daemon.json is no longer owned by the moby-engine package, be that some %post trickery or enlightening moby-engine to assume a default path to docker-proxy. |
Opened this upstream: moby/moby#47804 |
Upstream PR is merged. |
ACK. Backporting the change into Azure Linux 2.0 now so we can drop the /etc/docker/daemon.json file. |
The moby-engine-24.0.9-6.cm2.x86_64 package has just been published and no longer provides the |
Describe the bug
#8556 included a change that includes sane defaults in daemon.json. However, any consumer that deploys config using a configuration package now has a conflict.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Since docker does not have a drop-in system or any other kind of composability for its config, the moby-engine package should not 'own'
/etc/docker/daemon.json
.It might be a good idea to install a default in
/etc/docker/daemon.json.default
and copy it to/etc/docker/daemon.json
in postinst if this file does not exist. That still achieves the goal of shipping sane defaults, while not taking ownership of the file.The text was updated successfully, but these errors were encountered: