Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
docker: Error response from daemon: service endpoint with name already exists.
See original GitHub issueTrying to deploy my Meteor app to a fresh DigitalOcean droplet. mup setup runs just fine but running mup deploy gives me this:
Started TaskList: Start Meteor
[123.456.78.910] - Start Meteor
[123.456.78.910] x Start Meteor: FAILED
-----------------------------------STDERR-----------------------------------
Error response from daemon: No such container: myapp-frontend
Error response from daemon: No such container: myapp-nginx-letsencrypt
Error response from daemon: No such container: myapp-nginx-proxy
docker: Error response from daemon: service endpoint with name myapp already exists.
-----------------------------------STDOUT-----------------------------------
myapp
Removed myapp-frontend
Removed myapp-nginx-letsencrypt
Removed myapp-nginx-proxy
Using default tag: latest
latest: Pulling from kadirahq/meteord
Digest: sha256:7ec54d5fafc11acbcc82f3e555fddce8e4742ddeda05a64997f2a10e3c04137e
Status: Image is up to date for kadirahq/meteord:latest
Pulled kadirahq/meteord
cd19e3ea19ef8e6042153e0e7da0af7ed07b3a4a916d251d62d4c30791ca0432
----------------------------------------------------------------------------
(node:15428) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error:
-----------------------------------STDERR-----------------------------------
Error response from daemon: No such container: myapp-frontend
Error response from daemon: No such container: myapp-nginx-letsencrypt
Error response from daemon: No such container: myapp-nginx-proxy
docker: Error response from daemon: service endpoint with name myapp already exists.
-----------------------------------STDOUT-----------------------------------
myapp
Removed myapp-frontend
Removed myapp-nginx-letsencrypt
Removed myapp-nginx-proxy
Using default tag: latest
latest: Pulling from kadirahq/meteord
Digest: sha256:7ec54d5fafc11acbcc82f3e555fddce8e4742ddeda05a64997f2a10e3c04137e
Status: Image is up to date for kadirahq/meteord:latest
Pulled kadirahq/meteord
cd19e3ea19ef8e6042153e0e7da0af7ed07b3a4a916d251d62d4c30791ca0432
----------------------------------------------------------------------------
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Error response from daemon: service endpoint with name
docker : Error response from daemon: service endpoint with name qc.T8 already exists. However, there is no container with this name. > docker...
Read more >"endpoint with name XX already exists in network" can't ...
Describe the results you received: docker: Error response from daemon: endpoint with name mycontainer already exists in network bridge.
Read more >service endpoint with name 'container name' already exists - IBM
The Docker containers fail to start with the error “Error response from daemon: service endpoint with name <container_name> already exists.” ...
Read more >Error response from daemon: endpoint with name XXX ...
Error response from daemon : endpoint with name XXX already exists in network bridge. I think the #1642 (closed) bug is back in...
Read more >Why do I get the error Error response from daemon
Why do I get the error Error response from daemon: service endpoint with name logrotate_crond already exists while updating OSP13 ?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems to be a docker bug. When the container is removed, docker sometimes can’t disconnect the container from the network I run on the server:
Then I can deploy normally
What can be done is to update the startup script to include the command above after the ‘docker rm -f AppName’
PR Merged.