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.
Error response from daemon: driver failed programming external connectivity on endpoint
See original GitHub issue -----------------------------------STDERR----------------------------------- Removing docker containers. Errors about nonexistent endpoints and containers are normal. Error response from daemon: No such container: myroutes Error response from daemon: endpoint myroutes not found Error response from daemon: No such container: myroutes-frontend Error response from daemon: endpoint myroutes-frontend not found Error response from daemon: No such container: myroutes-nginx-letsencrypt Error response from daemon: endpoint myroutes-nginx-letsencrypt not found Error response from daemon: No such container: myroutes-nginx-proxy Error response from daemon: endpoint myroutes-nginx-proxy not found Finished removing docker containers docker: Error response from daemon: driver failed programming external connectivity on endpoint myroutes (8231a8806fda11ab47b00e17547623f42ecf8c68b56ac483ede958ad996135b3): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use. -----------------------------------STDOUT----------------------------------- base: Pulling from abernix/meteord Digest: sha256:9ed85313621010dd27a08054ae9225aa1f31798647fbcfdc9cc082181c6f9c97 Status: Image is up to date for abernix/meteord:base Pulled abernix/meteord:base 8e0866a9c801125fba4ebd306ccf831b91183241034576313c3ab564fb4e9d4c ----------------------------------------------------------------------------
Just tried deploying a new version of my meteor up with Meteor Up. This error appeared. I already tried:
- service docker restart on the droplet.
- mup restart
I just keep redeploying, it does not seem to help. Its quite urgent, because now the site is down.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@vfoley, I had the same problem on Windows 10. Restarting docker fixed it. Thanks for the advice, you gave me my sanity back…
for anyone having this issue just do
docker psthen get the id of the container that is running on port 80
sudo docker stop IDand it will fix it