[JENKINS-59777] nested docker.withRegistry() does not work

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: docker-commons-plugin, docker-workflow-plugin
Labels:
None
Environment:
Jenkins 2.190.1
docker-workflow-plugin 1.21
docker-commons 1.15

Similar Issues:
Powered by SuggestiMate

Show

With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:

node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}

From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

~~Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files~~
~~This MR introduced the env variables - specifically `DOCKER_CONFIG`~~
-~~Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with~~ --https://issues.jenkins-ci.org/browse/JENKINS-52737---
~~Made a MR for to use the latest docker-commons:~~ ~~[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]~~
Update – Fixes need on the docker-commons logic. MR here: https://github.com/jenkinsci/docker-commons-plugin/pull/82

links to

[GitHub] Docker Commons Plugin PR #82

Art V created issue - 2019-10-14 11:52

Art V made changes - 2019-10-14 11:59

Description

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

** Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

Art V made changes - 2019-10-14 11:59

Component/s

New: docker-commons-plugin [ 20628 ]

Art V made changes - 2019-10-14 12:00

Environment

Original: Jenkins 2.190.1
docker-workflow-plugin 1.21

New: Jenkins 2.190.1
docker-workflow-plugin 1.21
docker-commons 1.15

Art V made changes - 2019-10-14 12:14

Issue Type

Original: Task [ 3 ]

New: Bug [ 1 ]

Art V made changes - 2019-10-14 12:17

Description

Original: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

** Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

** Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737
Made a MR for to use the latest docker-commons: [https://github.com/jenkinsci/docker-workflow-plugin/pull/193]

Art V made changes - 2019-10-14 12:18

Description

Original: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

** Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737
Made a MR for to use the latest docker-commons: [https://github.com/jenkinsci/docker-workflow-plugin/pull/193]

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737
Made a MR for to use the latest docker-commons: [https://github.com/jenkinsci/docker-workflow-plugin/pull/193]

Art V made changes - 2019-10-15 11:52

Description

Original: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737
Made a MR for to use the latest docker-commons: [https://github.com/jenkinsci/docker-workflow-plugin/pull/193]

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* -Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737-
-Made a MR for to use the latest docker-commons:- [-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]
* Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]

Art V made changes - 2019-10-15 11:55

Assignee

New: Jesse Glick [ jglick ]

Art V made changes - 2019-10-15 12:17

Description

Original: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* -Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with https://issues.jenkins-ci.org/browse/JENKINS-52737-
-Made a MR for to use the latest docker-commons:- [-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]
* Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* --Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with- -https://issues.jenkins-ci.org/browse/JENKINS-52737--
-Made a MR for to use the latest docker-commons:- -[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]-
* Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]

Art V made changes - 2019-10-15 12:18

Description

Original: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]
This MR introduced the env variables - specifically `DOCKER_CONFIG`

* --Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with- -https://issues.jenkins-ci.org/browse/JENKINS-52737--
-Made a MR for to use the latest docker-commons:- -[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]-
* Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]

New: With the previous behavior of docker-workflow-plugin (1.15) I was able to nest my `docker.withRegistry()` calls so I can access numerous registries at the same time.

Example:
{code:java}
node('docker') {
    docker.withRegistry('https://repo1.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
        docker.withRegistry('https://repo2.private.com', '5d243c54-3d2c-42e3-9c3d-35c1cbe61ddd') {
            sh('docker pull repo1/library/image:latest')
            sh('docker pull repo2/libraryimage:latest')
        }
    }
}
{code}
From the output it looks like each credential is stored in it's own file per registry. My assumption is that with nested logins, it should be in the same credential store/file?

Is there any workaround for this?

* -Update – after more investigation – think this is more related to the docker-commons plugin - think it's related to this MR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/140/files]-
-This MR introduced the env variables - specifically `DOCKER_CONFIG`-
* --Update – further investigation – there has been an update to docker-commons-plugin that fixed this issue with- -https://issues.jenkins-ci.org/browse/JENKINS-52737--
-Made a MR for to use the latest docker-commons:- -[-https://github.com/jenkinsci/docker-workflow-plugin/pull/193-]-
* Update – Fixes need on the docker-commons logic. MR here: [https://github.com/jenkinsci/docker-commons-plugin/pull/82]

Assignee:: Jesse Glick

Reporter:: Art V

Votes:: 5 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 2019-10-14 11:52

Updated:: 2019-10-18 07:36

Jenkins

Details

Description

Attachments

Issue Links

Activity

People

Dates