On Fri, 12 Sep 2014 15:44:48 -0600 Tianon Gravi <admwig...@gmail.com> wrote: > 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 just did debcheckout docker.io, commented out disable-systemd-socket-activation.patch, addded the socket to docker.io.install and rebuilt. I uninstalled the current docker.io package, installed the new one, and docker.socket is correctly owned by root:docker. This is running under systemd 215-5+b1. Perhaps the backported patch in 208 had a bug that was corrected somewhere before 215 was released? Note that systemd 215 is in jessie now. Please revert the patch so we can rely on socket activation by default :). -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
