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#40847 - [docker] Please add docker.socket file

Attached to Project: Community Packages
Opened by Tobias Hunger (hunger) - Saturday, 14 June 2014, 21:54 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 24 July 2014, 22:59 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:

Docker ships with a systemd service file for socket activation for a while now. Please add that to the docker package. It makes docker more robust since anything depending on docker will just socket-activate it.

Please also make that the recommended way to start docker.


Additional info:
* docker 1.0.0-1


Steps to reproduce:
* Install docker
* run pacman -Ql docker

Expected result:
docker.socket file is found in the list of files installed by the docker package

Actual result:
Only a docker.service file is found.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Thursday, 24 July 2014, 22:59 GMT
Reason for closing:  Implemented
Additional comments about closing:  1:1.1.2-1
Comment by Sébastien Luttringer (seblu) - Saturday, 05 July 2014, 22:12 GMT
currently, doing a "systemctl enable docker.service" doesn't works with this set of systemd units.

The line Also=docker.socket in [Install] section is missing. This should be reported upstream.
Comment by Sébastien Luttringer (seblu) - Monday, 07 July 2014, 00:34 GMT
Please, reopen when docker.service is fixed.
Comment by Tobias Hunger (hunger) - Thursday, 17 July 2014, 14:44 GMT
  • Field changed: Percent Complete (100% → 0%)
The service file is updated to work with socket activation, of course it does not work when started solo.

If you want that you will need to ship an additional service unit to do that. Upstream seems to prefer socket activation (which is way more convenient since you can have units starting dicker images without declaring dependencies on docket. Service and having those race the docker daemon coming up).

Comment by Sébastien Luttringer (seblu) - Wednesday, 23 July 2014, 22:57 GMT
Should be ok in 1:1.1.1-2. Could you confirm that upgrade is smooth?
Comment by Tobias Hunger (hunger) - Thursday, 24 July 2014, 18:26 GMT
Upgrading will be a bit tricky since I just reinstall my docker server machine whenever there is a arch package update effecting it.

I'll try to find another machine to test this on.

Loading...