https://bugzilla.redhat.com/show_bug.cgi?id=1119282
Lars Kellogg-Stedman lars@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lars@redhat.com
--- Comment #8 from Lars Kellogg-Stedman lars@redhat.com --- Note that you can work around this issue in Fedora 20 like this:
systemctl stop docker.socket systemctl disable docker.socket systemctl disable docker
cat > /etc/systemd/system/docker.service <<EOF [Unit] Description=Docker Application Container Engine Documentation=http://docs.docker.io After=network.target
[Service] Type=notify EnvironmentFile=-/etc/sysconfig/docker ExecStart=/usr/bin/docker -d --selinux-enabled --dns 172.17.42.1 Restart=on-failure LimitNOFILE=1048576 LimitNPROC=1048576
[Install] WantedBy=multi-user.target EOF
systemctl enable docker systemctl start docker
This disable socket activation for docker, which means that systemd is no longer responsible for creating the docker socket. The docker daemon itself will create the socket, and will create it owned by the "docker" group (or any other group you specify in the --group command line option).
This change will persist after a reboot (unlike manually chmod'ing the socket created by systemd).