Discussion Docker/Portainer Error: "container already exists" when starting container

Status
Not open for further replies.

designgears

Full Member
Original poster
Staff
Local time
12:05 PM
Jan 21, 2018
35
17
I've seen this a few times now, usually after docker updates, very simple way to fix it, get the container id and run this command and everything will be back to normal :D

docker-containerd-ctr --address /run/docker/containerd/docker-containerd.sock --namespace moby c rm <containerd id>
 

Admin9705

Administrator
Project Manager
Local time
2:05 PM
Jan 17, 2018
4,760
1,812
I've seen this a few times now, usually after docker updates, very simple way to fix it, get the container id and run this command and everything will be back to normal :D

docker-containerd-ctr --address /run/docker/containerd/docker-containerd.sock --namespace moby c rm <containerd id>
sorry @designgear little confused about what your posting :D
 
Assists Greatly with Development Costs

designgears

Full Member
Original poster
Staff
Local time
12:05 PM
Jan 21, 2018
35
17
haven't gotten this, but had this happen for something before. what is the actually causes? have to delete it out?
It doesn't delete anything, just removes the container from moby, no data lose or anything, just start the container afterwards.
 
Status
Not open for further replies.

Maintenance Donations

Recommend NewsGroups

      Up To a 58% Discount!