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#42167 - [docker] no configuration file

Attached to Project: Community Packages
Opened by Justin Dray (justin8) - Monday, 29 September 2014, 04:40 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 30 September 2014, 18:02 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
There is currently no configuration file (like Debian's /etc/default/docker or RHEL's /etc/sysconfig/docker). This should just need a one line change to the service file to support changes in this manner.

Additional info:
* package version(s)
All
* config and/or log files etc.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 30 September 2014, 18:02 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#41036 
Comment by Doug Newgard (Scimmia) - Monday, 29 September 2014, 05:36 GMT
What change to the service file? Is this the same as  FS#41036 ?
Comment by Justin Dray (justin8) - Monday, 29 September 2014, 06:02 GMT
Sort of. I hadn't seen that one when searching to see if this had been requested already. But this would be to have EnvironmentFile to allow global settings such as httpproxy and such.

If you check out the service file that comes with the centos/rhel packages you can see what I mean. ( http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-0.11.1-22.el7.centos.x86_64.rpm ) The Debian packages have an example /etc/default with actual contents, but the service command itself doesn't necessarily have to change since docker allows settings things like this via environment variables.

Apparently my google-fu is weak today, but here is an example from the coreos documentation, where they change the proxy using 'Environment=HTTP_PROXY=foo':
https://coreos.com/docs/launching-containers/building/customizing-docker/

The default config could just be a blank file like the CentOS/RHEL one.
Comment by Bartłomiej Piotrowski (Barthalion) - Monday, 29 September 2014, 07:10 GMT
We use upstream files for systemd service and related files so better report it there.
Comment by Justin Dray (justin8) - Monday, 29 September 2014, 08:22 GMT
Will do. Thanks.

Edit: I actually just realized, wouldn't this part be distro specific anyway? I.e. Debian's /etc/default, our /etc/conf.d and so on. I'm not sure upstream would be the correct place for this change to be unless either all the distros converge on one config directory, or systemd mandates a specific one. Otherwise upstream apps would be reverting back to having a different service file per distro.

Loading...