This may be new behavior (I'm using docker 1.6 and systemd 208), but when I attempt to start a container by having a unit file's ExecStart command run "docker start", as described in spcContainers.md, the docker daemon starts the container in a new scope, the docker client exits, systemd notices that the unit file's process hierarchy is empty, and systemd then runs the ExecStop command, which runs "docker stop".
This may be new behavior (I'm using docker 1.6 and systemd 208), but when I attempt to start a container by having a unit file's ExecStart command run "docker start", as described in
spcContainers.md, the docker daemon starts the container in a new scope, the docker client exits, systemd notices that the unit file's process hierarchy is empty, and systemd then runs the ExecStop command, which runs "docker stop".