Andreas/docker-cheat-sheet
1
0
Fork 0
mirror of https://github.com/wsargent/docker-cheat-sheet.git synced 2025-12-16 15:10:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update networking in a live container

Browse source 
Provide documentation to map an additional port in a running container.
This commit is contained in:
Alejandro Sánchez Acosta 2016-06-17 10:59:16 -07:00 • committed by GitHub
parent 8eece99f9b
commit 8e35472d52
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -348,7 +348,11 @@ You can tell Docker that the container listens on the specified network ports at
EXPOSE <CONTAINERPORT> EXPOSE <CONTAINERPORT>
``` ```
But note that EXPOSE does not expose the port itself, only `-p` will do that. But note that EXPOSE does not expose the port itself, only `-p` will do that. To expose the container's port on your localhosts port:
```
iptables -t nat -A DOCKER -p tcp --dport <LOCALHOSTPORT> -j DNAT --to-destination <CONTAINERIP>:<PORT>
```
If you're running Docker in Virtualbox, you then need to forward the port there as well, using [forwarded_port](https://docs.vagrantup.com/v2/networking/forwarded_ports.html). It can be useful to define something in Vagrantfile to expose a range of ports so that you can dynamically map them: If you're running Docker in Virtualbox, you then need to forward the port there as well, using [forwarded_port](https://docs.vagrantup.com/v2/networking/forwarded_ports.html). It can be useful to define something in Vagrantfile to expose a range of ports so that you can dynamically map them: