[JENKINS-38135] docker plugin reads legacy network setting from docker

In case the container exposes the SSH port on 0.0.0.0 and the docker daemon is running on a unix socket, the plugin reads the NetworkSettings.IPAddress field from the docker container to determine what host to connect to in order to talk to the container. However, the field is only filled when the container runs with the default "bridge" network. If another network is used (e.g., if a custom network is configured in the "Network" field of the docker template setting) this field is empty and the field NetworkSettings..IPAddress has to be used. (cf. https://github.com/docker/docker/issues/21658#issuecomment-203527083).

---
Originally reported by amerkel, imported from: docker plugin reads legacy network setting from docker

• status: Open
  
• priority: Minor
  
• component(s): docker-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20260709-204134
  

Raw content of original issue

In case the container exposes the SSH port on 0.0.0.0 and the docker daemon is running on a unix socket, the plugin reads the NetworkSettings.IPAddress field from the docker container to determine what host to connect to in order to talk to the container. However, the field is only filled when the container runs with the default "bridge" network. If another network is used (e.g., if a custom network is configured in the "Network" field of the docker template setting) this field is empty and the field NetworkSettings.<network name>.IPAddress has to be used. (cf. https://github.com/docker/docker/issues/21658#issuecomment-203527083).

• environment: docker plugin 0.16.1