Hello!
Posting this here, because I am not able create an account to create a Jira issue. Yesterday our jenkins installation (2.73.1) proposed to update the Docker plugin to 0.18. Reading the plugins notes I reconfigured our cloud settings. A number of issues occurred. The plugin no longer assumes 4243 as default port. But that’s ok and can be configured. The plugin now always try to check a docker registry to start a docker container. If no registry is configures a fallback registry is used. In our situation: We have no registry. Our docker hosts have a fixed set of custom images that are used. No registry involved. The effect is, that many temporary slaves are shown on as executors, but none is really started on the hosts. Docker log on the hosts shows failed pull attempts. Docker ps shows no containers Playing with the configuration, sometimes a docker container could be started (No idea how that worked, with the issue mentioned above). Docker ps showed the started containers, but immediately terminated them. Somehow ssh always got connection refused. (We are using a user/pw stored in the images). I see those messages in the log of the spawned slave nodes. Reverting the plugin to version 16.2 resolved all those issues. If information, like our current docker configuration is needed, I am happy to provide it. Thank you in advance, Gunther -- 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/d0e6b348-fd77-4a8c-896d-349aa32cd648%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
