Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44656 - docker daemon configurations getting lost with every update

Attached to Project: Community Packages
Opened by Mehran (SeMeKh) - Monday, 20 April 2015, 08:09 GMT
Last edited by Ike Devolder (BlackEagle) - Monday, 20 April 2015, 09:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Every time `docker` package receives an update, the file `/usr/lib/systemd/system/docker.service` is replaced with the new content, and thus every host-specific options for the daemon (e.g. storage driver) are lost. Other distributions (like debian) provide a `/etc/defaults/docker` file to hold those host-specific options.
This task depends upon

Closed by  Ike Devolder (BlackEagle)
Monday, 20 April 2015, 09:08 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Ike Devolder (BlackEagle) - Monday, 20 April 2015, 09:07 GMT
that is normal, you can override host specific things in /etc/systemd/system/docker.service

the most simple approach is to copy /usr/lib/systemd/system/docker.service to /etc/systemd/system/ and make your changes

or you could do it 'the right way' by creating /etc/systemd/system/docker.service and use:

.include /usr/lib/systemd/system/docker.service

[Service]
ExecStart=my overridden command

...
Comment by Ike Devolder (BlackEagle) - Monday, 20 April 2015, 09:08 GMT
so this can be closed with note: not a bug

Loading...