https://bugzilla.redhat.com/show_bug.cgi?id=1096293
Bug ID: 1096293
Summary: `docker start` doesn't fail on started container
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Depends On: 1090071
+++ This bug was initially created as a clone of Bug #1090071 +++
Description of problem:
On older (0.9) docker, the `docker start $running_container` failed. The new
0.10.2 version just prints the container name and proceeds.
Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
Always
Steps to Reproduce:
1. docker run -i -t -name test fedora bash
2. docker start test
Actual results:
[root@t530 ~]# docker start test
test
[root@t530 ~]# echo &?
0
Expected results:
[root@t530 ~]# docker start test
Error: Cannot start container test: The container
429d709bc86c037b09e9f74dfab40aa33dc19bcf3109daf3f5b2fbbd3c6df297 is already
running.
2014/04/22 15:29:28 Error: failed to start one or more containers
[root@t530 ~]# echo &?
1
--- Additional comment from Lukas Doktor on 2014-05-05 03:38:57 EDT ---
Upstream Docker version 0.10.0, build dc9c28f/0.10.0 has the same issue
(silently passes even thought the container was already running)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1090071
[Bug 1090071] `docker start` doesn't fail on started container
--
You are receiving this mail because:
You are on the CC list for the bug.