fleet - database container

[PierreKircher]

they dont remove the name on unexpect reboot

-- Logs begin at Sun 2014-09-21 18:29:34 UTC. --
Sep 24 01:32:12 core1.c.graphite-sphere-686.internal docker[1126]: Pulling repository paulczar/percona-galera
Sep 24 01:32:19 core1.c.graphite-sphere-686.internal systemd[1]: Started database-1.
Sep 24 01:32:19 core1.c.graphite-sphere-686.internal sh[1174]: 2014/09/24 01:32:19 Error response from daemon: Conflict, The name database-1 is already assigned to 632648f90cbb. You have to delete (or rename) that container to be able to assign database-1 to a container again.
Sep 24 01:32:19 core1.c.graphite-sphere-686.internal systemd[1]: database-1.service: main process exited, code=exited, status=1/FAILURE
Sep 24 01:32:19 core1.c.graphite-sphere-686.internal docker[1193]: database-1
Sep 24 01:32:19 core1.c.graphite-sphere-686.internal systemd[1]: Unit database-1.service entered failed state.
Sep 24 01:35:40 core1.c.graphite-sphere-686.internal systemd[1]: Stopped database-1.

• unitfiles need some refactoring .. ill PR as soon as i have changes in place ..

Thanks for all the hard work !

[paulczar]

good catch! probably if the container of that name already exists we should just start it rather than running a new one.