[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist

[r...@akom.net (JIRA)]

Title: Message Title

Alexander Komarov edited a comment on JENKINS-59790   Re: Container cannot connect to node because it doesn't exist For those of us that do want to use *JNLP* rather than *Attach* mode, here is a quick and dirty workaround that has proven to stabilize docker launching under heavy load (in my case, a matrix job spawning 70 containers simultaneously).  All it does is re-run the JNLP script a few times in case the master wasn't ready.  Without this, I was left with a ton of stopped containers and no resources. I simply change the *ENTRYPOINT* in my images from the default (*/usr/local/bin/jenkins-agent* script from [jenkins/jnlp-slave)|https://hub.docker.com/r/jenkinsci/jnlp-slave/] to this script:   {code:java} #!/bin/bash ACTUAL_ENTRYPOINT=/usr/local/bin/jenkins-slave # sleep between retries, if needed (s) SLEEP=5   # Try to reconnect this many times TRIES=3 # Stop retrying after this many seconds regardless MAXTIME=60 # Do not retry if we're running bash to debug in this container # more than 1 arg is probably jenkins jnlp start if [ $# -eq 1 ] ; then   exec $* fi START=$(date +%s) while [ $TRIES -gt 0 ] && [ $(($(date +%s) - $START)) -lt $MAXTIME ] && ! $ACTUAL_ENTRYPOINT $* ; do   CODE=$?   echo "$ACTUAL_ENTRYPOINT exited [$CODE], waiting $SLEEP seconds and retrying"   sleep $SLEEP   TRIES=$(($TRIES - 1)) done echo "Exiting [$CODE] with $TRIES remaining tries and $(($(date +%s) - $START)) seconds elapsed" exit $CODE {code} and my Dockerfile looks like this: {code:java} FROM jenkins/jnlp-slave # directly or indirectly CMD [ "/bin/bash" ] ENTRYPOINT [ "entrypoint" ] {code} (My images have bash... for alpine you may want to change the shebang to /bin/sh)   For the record, network stability has been an issue for me with *Attach*.  Since I'm using classic Swarm, the connection is too complex and the connection is sometimes lost: {noformat} Master -> Swarm Manager -> Docker Host -> Container{noformat} With JNLP, it's simply: {noformat} Container -> Master{noformat}   [~oleg_nenashev], perhaps it may be worthwhile to integrate some (better than the above) retry logic in [jenkins-agent script|https://github.com/jenkinsci/docker-jnlp-slave/blob/master/jenkins-agent]?  (possibly after identifying the "unknown name" error from the master).   Happy to make a PR with some guidance. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.108.1573686660238%40Atlassian.JIRA.