Portainer: Failed to start potrainer after stop

Created on 31 Mar 2020  Â·  1Comment  Â·  Source: portainer/portainer

Question:
How can I start Portainer after stop?

I have successfully start it

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker stop portainer

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker: Error response from daemon: Conflict. The container name "/portainer" is already in use by container "54a6d7bebe3d333367b5e5dcc8633bfa13d2b406b5aa41ac29ee2ce4b000ff9b". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

Most helpful comment

Docker start portainer

Rgds,

Neil Cresswell

On 1/04/2020, at 4:46 AM, m3dbedb notifications@github.com wrote:



Question:
How can I start Portainer after stop?

I have successfully start it

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker stop portainer

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker: Error response from daemon: Conflict. The container name "/portainer" is already in use by container "54a6d7bebe3d333367b5e5dcc8633bfa13d2b406b5aa41ac29ee2ce4b000ff9b". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_3668&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=fgjGA2fhQYjTOrDepBLMTt0xn5bdfetl-YwEYY65OEk&s=dHo7W-qSYjA_iyKcjntJh8GAf7XCCqca6_0Vnmi1Esg&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AFQ2XFOZI52JSW23DFPBXOTRKIF4HANCNFSM4LXVDTOQ&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=fgjGA2fhQYjTOrDepBLMTt0xn5bdfetl-YwEYY65OEk&s=btiwDBaRnZpLeCNOrV0iNxX2CSGqwp_a48kxB6ci240&e=.

>All comments

Docker start portainer

Rgds,

Neil Cresswell

On 1/04/2020, at 4:46 AM, m3dbedb notifications@github.com wrote:



Question:
How can I start Portainer after stop?

I have successfully start it

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker stop portainer

docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

docker: Error response from daemon: Conflict. The container name "/portainer" is already in use by container "54a6d7bebe3d333367b5e5dcc8633bfa13d2b406b5aa41ac29ee2ce4b000ff9b". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_3668&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=fgjGA2fhQYjTOrDepBLMTt0xn5bdfetl-YwEYY65OEk&s=dHo7W-qSYjA_iyKcjntJh8GAf7XCCqca6_0Vnmi1Esg&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AFQ2XFOZI52JSW23DFPBXOTRKIF4HANCNFSM4LXVDTOQ&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=fgjGA2fhQYjTOrDepBLMTt0xn5bdfetl-YwEYY65OEk&s=btiwDBaRnZpLeCNOrV0iNxX2CSGqwp_a48kxB6ci240&e=.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

chrisvanderpennen picture chrisvanderpennen  Â·  3Comments

cbrherms picture cbrherms  Â·  3Comments

rnz picture rnz  Â·  3Comments

WTFKr0 picture WTFKr0  Â·  4Comments

neilqin picture neilqin  Â·  3Comments