You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found a bug where if you configure the Docker plugin such as:
Docker Host: 172.17.42.1
Where the Jenkins Master is a Docker Container itself.
When Jenkins spawns new salves in the configuration
it incorrectly tries to perform an SSH connection to 172.17.42.1:49152 for example rather than the
actual IP Address of the newly formed Container.
The text was updated successfully, but these errors were encountered:
I've found a bug where if you configure the Docker plugin such as:
Docker Host: 172.17.42.1
Where the Jenkins Master is a Docker Container itself.
When Jenkins spawns new salves in the configuration
it incorrectly tries to perform an SSH connection to
172.17.42.1:49152 for example rather than the
actual IP Address of the newly formed Container.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14
.
I've found a bug where if you configure the Docker plugin such as:
Docker Host: 172.17.42.1
Where the Jenkins Master is a Docker Container itself.
When Jenkins spawns new salves in the configuration
it incorrectly tries to perform an SSH connection to
172.17.42.1:49152
for example rather than theactual IP Address of the newly formed Container.
The text was updated successfully, but these errors were encountered: