On Tue, 24 Jun 2014 11:15:36 -0400 Felipe Sateler <fsate...@debian.org> wrote: > Enabling socket activation should prevent races when starting up docker > containers at boot time, such as "is the docker daemon running?".
So, I've been working on this, especially since upstream deprecated and removed their non-socket-activation service file and also because systemd 208-8 in jessie includes the necessary patches for SocketUser and SocketGroup to work (which is actually the reason for the delay in getting 1.2.0 out). The problem I've been running into is that on initial install, the socket is owned by "root:root", but after a simple "systemctl restart docker.socket" it is fixed and properly "root:docker" as specified. I've played with all kinds of combinations of one or both of these: (which are partly borrowed/learned from acpid and lvm2 d/rules files) | override_dh_systemd_enable: | dh_systemd_enable -pdocker.io --no-enable docker.service | dh_systemd_enable -pdocker.io docker.socket | | override_dh_systemd_start: | dh_systemd_start -pdocker.io --no-start docker.service | dh_systemd_start -pdocker.io docker.socket Including playing with "--restart-after-upgrade" which I've seen some other packages use for socket activation as well, but no dice no matter what I do. If this problem sounds familiar to anyone and there's a solution I haven't found, please say so. I've been tearing my hair out something fierce fighting with it. :) (... and now, I'm off to go prep 1.2.0 for release with socket activation patched back out for now, so at least we can have new Dockers while we figure out this issue.) ♥, - Tianon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
