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.
file /etc/docker/daemon.json from install of azuredb-dataplane-common-0.0.19-1.cm2.noarch conflicts with file from package moby-engine-24.0.9-1.cm2.x86_64
To Reproduce
Steps to reproduce the behavior:
- Create a package that deploys custom config using /etc/docker/daemon.json
- Try to install your package on a system where
- Scroll down to '....'
- See error
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.
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.defaultand copy it to/etc/docker/daemon.jsonin postinst if this file does not exist. That still achieves the goal of shipping sane defaults, while not taking ownership of the file.