Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exposing port is not necessary #2

Open
pdumais opened this issue Jan 30, 2019 · 3 comments
Open

Exposing port is not necessary #2

pdumais opened this issue Jan 30, 2019 · 3 comments

Comments

@pdumais
Copy link

pdumais commented Jan 30, 2019

Do you really have to expose ports using "-p" in docker run? You are using net=host, I think this would be unnecessary. Can you confirm?

@pedrxd
Copy link

pedrxd commented Feb 26, 2019

If you use net=host is not necesary expose ports as it give the same network of the host to the docker. The question is why if you don't use net=host it doesn't work. What ports are necesary?

@dolchi21
Copy link

has anyone tried bridge network and mapping ports 50000-60000 for example?

@e2jk
Copy link

e2jk commented Feb 1, 2021

The cause seems to be that Multicast is needed.
See https://wiki.archlinux.org/index.php/ReadyMedia#iptables (ReadyMedia is the new name of minidlna)
Not sure yet how to enable that in Docker (seems like we're going to have an issue with the ttl, by default set to ! but needed to be set to 2 if the multicast packets are to be reaching inside the container?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants