DHCP and docker inspect about pipework HOT 5 CLOSED

Hi,

Unfortunately, the extra network interfaces created by pipework are not visible to Docker, and therefore, cannot be queried with the REST API.

Question: do you need to use IP addresses here? Couldn't you use the IP address of the host + mapped ports?

from pipework.

I want to start containers up dynamically from Jenkins, as I understand it the ports are not assigned dynamically I need to fix then when I call docker run -p. If that is correct then it means I have tovlidy every container rather than having n instances of 1 container. If it is possible to have dynamic port allocation then I can use host IP and the rest api to tell me the port. Is that possible?

from pipework.

You can have dynamic port allocation, no problem at all.

E.g., supposing that you want to start a container running a web server on port 80:

$ docker run -p 80 -d my_web_server
880af59a97f195470751f4a3e8569fb358b344dce2fa581199d2b06ae9f3294b
$ docker port 880af59a97f195470751f4a3e8569fb358b344dce2fa581199d2b06ae9f3294b 80
0.0.0.0:49157

Then you can connect to the host IP address on port 49157.

Does that help?

from pipework.

yes -sorry for late reply. All sorted now. Sorry for being a muppet.

from pipework.

No problem at all; I'm happy that we could help with this!

from pipework.