Controller does not come up when port 8080 is not bound about unifi-docker

[jacobalberty]

It runs fine with only specific ports bound, what does docker ps say about the ports for the running container?

[pfried]

It does not bind them somehow, usually i get an error if the ports cannot be bound. But this then may be a docker specific error:

The command i am running:
sudo docker run --rm -d -p 8442:8443 --net=host -v ~/unifi/data:/var/lib/unifi -v ~/unifi/logs:/var/log/unifi -v ~/unifi/run:/var/run/unifi --name unifi jacobalberty/unifi:unifi5

[pfried]

Thank you for the quick response, i think this issue is not related to this project, binding to the host network and specifying the ports may have some problems, if i do not specify the ports they get bound correctly to a ephemeral port range

[JohnnyMaccarone]

I actually have the same problem. Everything works until I try to bind the ports to the non-standard ones.
While I use the same command as pfried, I also don't see any ports being mapped when I check with 'docker ps'.
(I would need to run 10 containers on the same box, so changing those ports is required).

Not sure how to accomplish this.

[jacobalberty]

@JohnnyMaccarone If you need to run 10 containers mapping all of those ports may be a bit heavier than you should be doing. You should look into some of the more advanced docker networking options. Specifically the macvlan networking driver allows you to give containers routable ips.

https://blog.docker.com/2016/12/understanding-docker-networking-drivers-use-cases/

[JohnnyMaccarone]

Thanks for your quick response !
I'll have a look into your suggestion.
Cheers.

[pfried]

I did attach the container to a macvlan, a very helpful article on this issue:
http://collabnix.com/docker-17-06-swarm-mode-now-with-macvlan-support/