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.
Can't access the exposed ports in Swarm Deployment.
See original GitHub issueHeya
I got issues accessing the voting-app on a swarm deployment through docker stack.
- Does the
frontendoverlay-network not need to be marked asexternalin thedocker-stack.yml? - … and if so, needs to be created up front ? before the
docker stack deploy?
Thx for any help on making this work for me, Christian.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Docker swarm not exposing port
After starting using docker stack deploy -c myapp.yml myapp , I run the docker ps command and only see 8123/tcp in the PORTS...
Read more >Docker swarm mode - published ports are not exposed
When exposing ports in swarm mode, the container ports are not exposed. This is unexpected because similar commands in docker-compose or ...
Read more >How to expose docker swarm service ports only internally?
With docker swarm I don't know how to do this. It's possible to get the underlying container IP in a service, but I...
Read more >Traefik Docker Documentation
Configuring Docker Swarm & Deploying / Exposing Services ... If a container exposes multiple ports, or does not expose any port, then you...
Read more >Docker swarm not exposing port
I'm trying to run docker swarm on a single node and having trouble getting a docker app port exposed to the host. This...
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
I am facing the same,Helped me to resolve the same issue. Thanks a lot.
Did something change in the latest docker? I’m having the same issue.
I followed the steps in this repo, along with the steps here; https://docs.docker.com/get-started/part4/, but when visiting: 192.168.99.100 in my browser I’m getting a “refused to connect.” message.
I’m on the latest Docker, VirtualBox, and Mac OS 10.14 (Mojave)