orphaned containers are not removed

[ghostofthecode]

I have following simple services:

srv_0:
  image: busybox
  command: sleep 300
  links:
    - srv_1

srv_1:
  image: busybox
  command: sleep 300

They are successfully started with up command:

docker-compose up srv_0

CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                                   NAMES
3f553caaedfb        busybox                       "sleep 300"              18 seconds ago      Up 17 seconds                                                               dockercompose_srv_0_1
45bf185cc27f        busybox                       "sleep 300"              31 minutes ago      Up 18 seconds                                                               dockercompose_srv_1_1

Now srv_1 is deprecated and I replace it with srv_2:

srv_0:
  image: busybox
  command: sleep 300
  links:
    - srv_2

srv_2:
  image: busybox
  command: sleep 350

docker-compose up srv_0

still works successfully, but it leaves orphaned srv_1:

[vagrant@epplkraw0047t1 docker_compose]$ sudo docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                                   NAMES
5262677b73c9        busybox                       "sleep 300"              41 seconds ago      Up 40 seconds                                                               dockercompose_srv_0_1
922f5e4172b8        busybox                       "sleep 350"              33 minutes ago      Up 51 seconds                                                               dockercompose_srv_2_1
45bf185cc27f        busybox                       "sleep 300"              33 minutes ago      Up 2 minutes                                                                dockercompose_srv_1_1

👍

Seeing a similar issue for docker-compose run but not for docker-compose up as-of

docker-compose version 1.5.2, build 7240ff3

The default stop kill remove will not cleanup the run (leaked) container. At least docker-compose ps will now display the leaked container. Previously this was not the case.

Simple test

mkdir test; cd test; echo -e 'myservice:\n image: mongo:3' > docker-compose.yml

WORKS for docker-compose up

$ docker-compose up -d
Starting test_myservice_1
$ docker-compose stop
Stopping test_myservice_1 ... done
$ docker-compose rm -vf
Going to remove test_myservice_1
Removing test_myservice_1 ... done

FAILS for docker-compose run

$ docker-compose run -d myservice
test_myservice_run_1
$ docker-compose stop
$ docker-compose rm -vf
No stopped containers
$ docker-compose ps
        Name                  Command          State     Ports
----------------------------------------------------------------
test_myservice_run_1   /entrypoint.sh mongod   Up      27017/tcp

[dnephin]

I think this is a duplicate of #1477 which has a PR open for it (#2218)

[dnephin]

Closing as duplicate.