You’re supposed to be able to. You’ve started your container with the docker run -p option so the port is published on the host? You don’t have a restrictive host iptables firewall configuration that’s blocking it?
yes I run it like that. this container is more like a testbox. A box where I can go toany website I want without risking to contaminate other things for example because of malicious code. No personal data stored or anything else. the iptables is of course restricted but when you create a container by publishing the port, it opens autmatically the port on the forward table from docker so that’s not supposed to be a problem. Plus I can reach the 2 container outside.
You should never need this for most situations I know of. It’s also not (by default) routable or especially unique: my system and yours both probably have 172.17.0.0/16 Docker private networks, and if my host tried to get to 172.17.0.2 the packets would never leave my box.
that was I thought but it doesn’t seem to work and I’m a bit clueless on that one. Maybe could you try? the concerned container is 
warehouseman/xubuntu-x2go-phusion "/sbin/my_init" 3 days ago Up 22 hours 0.0.0.0:45117->22/tcp test