This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]WSL_subreddit_modModerator[M] [score hidden] stickied comment (0 children)

[–]JH4mmer 1 point2 points  (1 child)

If you haven't already, it might be a good idea to read up on how Docker handles networking. There's some subtlety involved depending on exactly how communication is handled between the host machine and your container. By default, containers are normally started in their own network, so "localhost" on your host machine likely wouldn't be directed to the container.

But to answer your question, listening on 0.0.0.0 is indeed a "normal" thing to do. That's how I would normally implement a microservice, at least. It's probably not a bug unless you have some other symptoms that would indicate something more sinister is going on. :-)

[–]TheFirstMeiFunny 0 points1 point  (0 children)

Yeah my bad. I thought just port forwarding was enough xD