Frustrating thing is that I definitely had this same exact setup working previously (jenkins master in docker container spawning slaves in sibling containers), albeit in the context of docker toolbox (boot2docker) running on windows, whereas I am now running against standard docker on linux.
On 20 October 2017 at 13:25, Martin Heg <[email protected]> wrote: > Yes - jenkins master running in container. > From the docker host I can manually ssh into the slave container with: > ssh -p *ephmeral_port* [email protected] > If I docker exec into the jenkins master I can also ssh into the slave > container using the docker host ip: > ssh -p *ephmeral_port* jenkins@*hostip* > > hmmmm..... > > On 20 October 2017 at 13:05, nicolas de loof <[email protected]> > wrote: > >> Is your jenkins master running in a docker container as well ? >> >> stacktrace seems to demonstrate failure to establish a route to >> 0.0.0.0:32791, even before any SSH authentication attempt >> >> 2017-10-20 12:16 GMT+02:00 Martin Heg <[email protected]>: >> >>> Thanks for your reply Nicolas. Yes I saw that suggestion in one of your >>> other posts and have already tried it but still seeing the same issue >>> unfortunately. >>> >>> On 20 October 2017 at 11:11, nicolas de loof <[email protected]> >>> wrote: >>> >>>> to use your own SSH credentials you need to disable the "SSH key >>>> management" option (title is unclear) >>>> with this option set the container is configured to rely on jenkins >>>> master Identity ssh key >>>> >>>> I'm working on a UI refactoring to avoid such confusing options >>>> >>>> 2017-10-20 11:38 GMT+02:00 <[email protected]>: >>>> >>>>> Just to add that the Docker plugin also recognises the slave container >>>>> as running as shown in this attachment. >>>>> >>>>> >>>>> <https://lh3.googleusercontent.com/-dwvQgB3E6S4/WenD9OpnTbI/AAAAAAAAAAM/zOJHAj-aEuQ32teM26AFPsAELCX8QAVvwCLcBGAs/s1600/screenshot.9.jpg> >>>>> >>>>> >>>>> On Friday, 20 October 2017 10:03:45 UTC+1, [email protected] wrote: >>>>>> >>>>>> Hi, >>>>>> I am getting this error on various versions of Jenkins and the >>>>>> docker-plugin including latest of both. >>>>>> My Jenkins master is running in a container. It successfully launches >>>>>> a docker container for the slave (using the evarga/jenkins-slave image) >>>>>> but >>>>>> then fails to connect with the error below. >>>>>> I can see my slave running with a docker ps and can even successfully >>>>>> connect to it via ssh on 0.0.0.0:32791 (or whatever the given >>>>>> ephmeral port is) using the same credentials configured in the docker >>>>>> agent >>>>>> template section. >>>>>> Any ideas really welcome as I'm now going round in circles trying to >>>>>> get this working. >>>>>> Thanks. >>>>>> >>>>>> >>>>>> [10/20/17 08:13:45] [SSH] Opening SSH connection to 0.0.0.0:32791. >>>>>> Connection refused (Connection refused) >>>>>> SSH Connection failed with IOException: "Connection refused (Connection >>>>>> refused)". >>>>>> java.io.IOException: There was a problem while connecting to >>>>>> 0.0.0.0:32791 >>>>>> at com.trilead.ssh2.Connection.connect(Connection.java:834) >>>>>> at com.trilead.ssh2.Connection.connect(Connection.java:703) >>>>>> at com.trilead.ssh2.Connection.connect(Connection.java:617) >>>>>> at >>>>>> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1284) >>>>>> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804) >>>>>> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793) >>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >>>>>> at java.lang.Thread.run(Thread.java:748) >>>>>> Caused by: java.net.ConnectException: Connection refused (Connection >>>>>> refused) >>>>>> at java.net.PlainSocketImpl.socketConnect(Native Method) >>>>>> at >>>>>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) >>>>>> at >>>>>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204) >>>>>> at >>>>>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) >>>>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) >>>>>> at java.net.Socket.connect(Socket.java:589) >>>>>> at >>>>>> com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:367) >>>>>> at >>>>>> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:480) >>>>>> at com.trilead.ssh2.Connection.connect(Connection.java:774) >>>>>> ... 9 more >>>>>> [10/20/17 08:13:45] Launch failed - cleaning up connection >>>>>> [10/20/17 08:13:45] [SSH] Connection closed. >>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/9359318d-f >>>>> 78f-432a-bd06-4c10768f2cdc%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/9359318d-f78f-432a-bd06-4c10768f2cdc%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Users" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/jenkinsci-users/cEKuC4GwP5I/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit https://groups.google.com/d/ms >>>> gid/jenkinsci-users/CANMVJzkXMLjco0tzp_rcZpcyQ-4xFMQNi9%3DKA >>>> AEK6-Z8r%3DLYMg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzkXMLjco0tzp_rcZpcyQ-4xFMQNi9%3DKAAEK6-Z8r%3DLYMg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/jenkinsci-users/CAHigaWxJMbmwMoMdXADbmwsYwgwsX8RpixHfqfZ >>> -nJZbj1rFjA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/CAHigaWxJMbmwMoMdXADbmwsYwgwsX8RpixHfqfZ-nJZbj1rFjA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/jenkinsci-users/cEKuC4GwP5I/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/jenkinsci-users/CANMVJznY_yeVFHw6GY0kj1Oj6Zrg04N9ws6D%2B >> EMXdfunYfe6Hg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJznY_yeVFHw6GY0kj1Oj6Zrg04N9ws6D%2BEMXdfunYfe6Hg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAHigaWwyffZrVaN5mNdXir5p0yOipWKrcZrNF6DijYrSjNT15w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
