Skip to content

Conversation

jbiel
Copy link

@jbiel jbiel commented Mar 12, 2020

This patch causes the docker login process to read the password from stdin rather than as an argument. Using an argument for the password causes issues with complex passwords (such as the JSON documents needed GCR) or passwords with special shell characters ($ especially.)

The --password-stdin flag was introduced in Docker version 17.07.0 so it's been around for a decent amount of time by now. The oldest supported version that doesn't have this flag (enterprise 17.06) is EOL on 2020-04-16, so perhaps this change could be merged in after that date.

This change will solve these open issues:

https://issues.jenkins-ci.org/browse/JENKINS-52761
https://issues.jenkins-ci.org/browse/JENKINS-53770

@jbiel
Copy link
Author

jbiel commented Jul 8, 2020

Can this PR please be considered for merging? If there are any issues with it please let me know. Thanks!

@tschaible
Copy link

@rsandell @oleg-nenashev this PR looks complete and addresses some open issues (i found myself here after running into an issue with a password containing an $ today)

There are a few other PRs that look complete, but do not have further activity.

Is this plugin still maintained? Has there been any discussion on potentially taking on more maintainers?

@oleg-nenashev
Copy link
Member

oleg-nenashev commented Apr 21, 2021 via email

@tschaible
Copy link

Is there any guidance on how to be more involved and potentially be a maintainer.

I've read the Jenkins guidance for "Adopt a Plugin", but it says the following.

First, make sure the plugin is not being actively maintained. Even in actively maintained plugins, there may be periods of lower developer activity. Don’t misinterpret failures to respond to questions or requests as the plugin being unmaintained!

That seems to apply to this plugin, so I'm just not sure how to get started in helping to move things forward.

@jbiel
Copy link
Author

jbiel commented Jan 13, 2022

@jbiel
Copy link
Author

jbiel commented Feb 3, 2022

@rsandell - any chance you could please review this?

@mgar
Copy link

mgar commented Mar 30, 2022

New build: https://ci.jenkins.io/job/Plugins/job/docker-commons-plugin/job/PR-86/7/artifact/org/jenkins-ci/plugins/docker-commons/1.20-rc369.ca0881662826/docker-commons-1.20-rc369.ca0881662826.hpi

@jbiel – we are also experiencing the same issue, and I tried to update the plugin with that artifact, but now I'm getting the following error:

Cannot perform an interactive login from a non TTY device

Any idea?

@rsandell rsandell added the bug label Aug 23, 2022
@rsandell rsandell merged commit 7159f44 into jenkinsci:master Aug 23, 2022
@moshavnik
Copy link

@mgar , @jbiel , we are also experiencing the same issue here while running withRegistry command inside a dind (docker in docker) container:
Cannot perform an interactive login from a non TTY device

@barney2k7
Copy link

This seems to break things for many people, see https://issues.jenkins.io/browse/JENKINS-69432 and https://issues.jenkins.io/browse/JENKINS-69436
@rsandell can this please be reverted and a new docker-commmons 1.21 published?

@nkalev
Copy link

nkalev commented Aug 26, 2022

This broke all of our builds, i would appreciate detailed usage description or a proper fix

rsandell added a commit that referenced this pull request Aug 26, 2022
[JENKINS-69432, JENKINS-69436] Revert #86 "docker login - get password from stdin"
@rsandell
Copy link
Member

Reverted in v. 1.21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants