[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Scott Williams commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Jesse Glick What docker login environment problem? Docker login works fine from CLI, ansible, or this plugin from 1.15.1 and previous. Between this and the breaking ENTRYPOINT in 1.15.x, I'm at my last straw with this plugin and possibly even Jenkins itself as Docker has become such a core of our operations. I'm happy to help test and possibly contribute code, but I just can't continue having my teams rely on a feature that has major regressions every update and the CloudBees devs keep dismissing the people reporting the issues and trying to fix them. It's never fun when we have to keep spending our time debugging and coding workarounds for this plugin rather than the code we're trying to test to begin with. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Scott Williams edited a comment on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Same here with an internal Docker registry. Docker login now fails with "401 unauthorized" after upgrading to 1.16.Reverting to 1.15.1 fixes works, so this appears to be a significant regression with 1 . 16. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Scott Williams commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Same here with an internal Docker registry. Docker login now fails with "401 unauthorized" after upgrading to 1.16. Reverting to 1.15.1 fixes works, so this appears to be a significant regression. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Scott Williams commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Note that with an argument delimited entrypoint, the command given (either via CMD or docker run command) will be appended after the entrypoint. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Scott Williams commented on JENKINS-49278 Re: cat command in docker agents not detected correctly I suspect JENKINS-49385 is a duplicate issue, but it is not resolved with the 15.1 update. The cat command still instantly fails with an argument delimited entrypoint in the Dockerfile (see comments therein). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49385) containers exit early in docker-workflow 1.15
Title: Message Title Scott Williams reopened an issue Problem persists with 15.1 update. Jenkins / JENKINS-49385 containers exit early in docker-workflow 1.15 Change By: Scott Williams Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49385) containers exit early in docker-workflow 1.15
Title: Message Title Scott Williams commented on JENKINS-49385 Re: containers exit early in docker-workflow 1.15 Sadly, 15.1 doesn't fix this issue at all. The problem is that neither will work with an argument delimited ENTRYPOINT as the ENTRYPOINT gets placed at the beginning and the command is tacked on to the end. $ docker run -t -d -u 0:0 -w /opt/jenkins/workspace/Zendesk-bulk -v /opt/jenkins/workspace/Zendesk-bulk:/opt/jenkins/workspace/Zendesk-bulk:rw,z -v /opt/jenkins/workspace/Zendesk-bulk@tmp:/opt/jenkins/workspace/Zendesk-bulk@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e a3af309c86bf5b2ad033f313de7dc875df1f71f1 cat $ docker top 1704cb59764ae62c736ffa4d78e1220bb0be3fb02931b54a4014a90f9ab0b920 -eo pid,comm This inevitably fails with a properly arg delimited ENTRYPOINT... java.io.IOException: Failed to run top '1704cb59764ae62c736ffa4d78e1220bb0be3fb02931b54a4014a90f9ab0b920'. Error response from daemon: Container 1704cb59764ae62c736ffa4d78e1220bb0be3fb02931b54a4014a90f9ab0b920 is not running Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
