When deleting a docker container, it looks as if the Docker plugin *stops* the container but does not *remove*. Given the following resource:
docker_dbserver:
type: "DockerInc::Docker::Container"
properties:
image: mysql
port_specs:
- 3306
port_bindings:
3306: 3306
env:
- MYSQL_ROOT_PASSWORD=secret
name: dbserver
volumes:
/srv/data_in_container: /var/tmp/data_on_host
If we successfully create the stack, we end up with:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ce51887391f7 mysql:5 "/entrypoint.sh mysq 54 seconds ago Up 53 seconds 0.0.0.0:3306->3306/tcp dbserver
If we delete the stack, Heat logs a successful deletion:
[req-46e8154b-66fe-4258-a9f6-c07a627a713b None] Deleting stack local
[-] deleting DockerContainer "docker_dbserver" [ce51887391f74488dd5f9bd3a106e23a3f52a118b7bdaaefab9026102f94d9c5] Stack "local" [a44c0941-2f09-4ee5-a14b-3234c7e6c8ab]
But `docker ps -a` shows that the container still exists:
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ce51887391f7 mysql:5 "/entrypoint.sh mysq About a minute ago Exited (-1) 41 seconds ago dbserver
This means that if one tries to re-create the stack, Heat will fail
with:
APIError: 409 Client Error: Conflict ("Conflict, The name dbserver is already assigned to ce51887391f7. You have to delete (or rename) that container to be able to assign dbserver to a container again.")
...and that point, you hit https:/