venkytv
commented
7 years ago That is a problem with named containers, I’m afraid. When upgrading, we’ll have to do a “docker rm” of the old container before creating a new one with “docker run”.
Maybe also something the run script can handle.
root@ansible:~# docker run --name pluribus-onie-ztpv9 --net=host --cap-add net_raw --cap-add net_admin --mount source=ztpvol,target=/ztpvol pluribus-onie-ztpv9 -d container_linux.go:265: starting container process caused "exec: \"-d\": executable file not found in $PATH" docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"-d\": executable file not found in $PATH". ERRO[0000] error waiting for container: context canceled root@ansible:~# docker run --name pluribus-onie-ztpv9 --net=host --cap-add net_raw --cap-add net_admin --mount source=ztpvol,target=/ztpvol pluribus-onie-ztpv9 docker: Error response from daemon: Conflict. The container name "/pluribus-onie-ztpv9" is already in use by container "a1e898b22984f111f9a4c169ce8eb53ba49ab981377710a4cafc23c735e90e98". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'. root@ansible:~#