[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title
Bruno Meneguello edited a comment on JENKINS-39952
Re: "Registry credentials" is not working with a private docker registry
Nearly 2020 and still having I'm using this issue with Kubernetes cloud and a docker-dind image .I just succeeded by adding a shell step with {{docker login ... before the step . }}
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.176574.1479864408000.5696.1576085820303%40Atlassian.JIRA.
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Bruno Meneguello commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Nearly 2020 and still having this issue. I just succeeded by adding a shell step with docker login ... before the step 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.176574.1479864408000.5583.1576075560270%40Atlassian.JIRA.
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Rehab Hassanein commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry I went on for hours in circles just to fix this at the end by adding an execute shell step to do the following: mv ~/.dockercfg ~/.dockercfg.old This fixed my issue. Thanks Ryan Currah for pointing out the exact issue with this file. 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Tenyo Grozev commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry The registry authentication stopped working for us after we upgraded from Docker 1.10 to 1.12, which now uses exclusively .docker/config.json instead of .dockercfg. This plugin only generates .dockercfg. As a workaround, I've logged in locally on the Docker host to generate the config.json. 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Another issue is that users keep selecting this option with invalid credentials and it breaks builds because it writes a file to /home/jenkins/.dockercfg with bad credentials and not everyone who uses that build slave cant pull images from docker.io. Is there some less persistent way to use the credentials? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah edited a comment on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Another issue is that users keep selecting this option with invalid credentials and it breaks builds. Because it writes a docker credentials file to /home/jenkins/.dockercfg with bad credentials. No one can pull from docker.io because we are getting auth errors against docker.io in all the jobs now. Now everyone Everyone who uses that build slave cant pull images because of one person's misconfiguration ina job . Is there some less persistent way to insert the credentials on a per job basis? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah edited a comment on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Another issue is that users keep selecting this option with invalid credentials and it breaks builds. Because it writes a docker credentials file to /home/jenkins/.dockercfg with bad credentials. Now no No one can pull from docker.io because we are getting auth errors against docker.io in all the jobs now. Now everyone who uses that build slave cant pull images from docker . io. Is there some less persistent way to insert the credentials on a per job basis? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah edited a comment on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Another issue is that users keep selecting this option with invalid credentials and it breaks builds because . Because it writes a docker credentials file to /home/jenkins/.dockercfg with bad credentials and not . Now no one can pull from docker.io because we are getting auth errors against docker.io in all the jobs now. Now everyone who uses that build slave cant pull images from docker.io. Is there some less persistent way to use insert the credentials on a per job basis ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah edited a comment on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry We thought we could use it for our private registry turns out this is not the case. We As Jenkins Enterprise customers we would love to be able to specify which registry the credentials are for. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Ryan Currah commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry We thought we could use it for our private registry turns out this is not the case. We would love to be able to specify which registry the credentials are for. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title nkcfan nkcfan reopened an issue Follow up with my question, and change the issue title accordingly. Thanks for helping! Jenkins / JENKINS-39952 "Registry credentials" is not working with a private docker registry Change By: nkcfan nkcfan Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title nkcfan nkcfan updated an issue Jenkins / JENKINS-39952 "Registry credentials" is not working with a private docker registry Change By: nkcfan nkcfan Summary: There is no " Configure Docker Registry : CloudBees Docker Build and Publish credentials " section in Jenkins/Configure System is not working with a private docker registry Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
