[JIRA] (JENKINS-61353) UnresolvedAddressException in JNLP client running in Docker container

[slide.o.mix@gmail.com (JIRA)]

Alex Earl moved an issue

Jenkins / JENKINS-61353 UnresolvedAddressException in JNLP client running in Docker container Change By: Alex Earl Project: Infrastructure Jenkins Key: INFRA JENKINS - 2424 61353 Workflow: classic default workflow JNJira + In-Review Component/s: _unsorted Component/s: docker Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated an issue

Jenkins / JENKINS-61353 UnresolvedAddressException in JNLP client running in Docker container

Change By: Mark Waite Component/s: docker-swarm-plugin Component/s: _unsorted

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-61353

Re: UnresolvedAddressException in JNLP client running in Docker container I suspect that there is an infrastructure failure on your site which is causing the DNS resolver to no longer return the IP address of the docker swarm agents. I doubt it is anything that the docker swarm plugin can resolve. If there is a bug, it is likely in the docker swarm code rather than in the swarm plugin.

Add Comment

[julian.breitung@edag.com (JIRA)]

Julian Breitung commented on JENKINS-61353

Re: UnresolvedAddressException in JNLP client running in Docker container

Hi, I don't think that we've an infrastructure failue here, because if it would be so, our whole company would collapse. The IP which is not resolved is the IP of the Jenkins server which hosts the docker-swarm-plugin and connects to the swarm agents. There is no problem with resolving the IP addresses of the docker swarm agents. The provided log output is out of the running docker-container on the docker-swarm which provides the JNLP client.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-61353

Re: UnresolvedAddressException in JNLP client running in Docker container

I should have been more clear. The DNS resolver that I suspect is failing is inside the docker swarm, not in your corporate infrastructure. I'm not a Docker swarm expert by any stretch, but I suspect there is a DNS resolver inside it which provides DNS resolution as docker images are executed on various nodes in the swarm.

Add Comment