-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Kubernetes master slave configuration. Registry is a private registry (v2).
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again.
Upon further testing, it looks like registry auth is not working at all:
docker-build-publish 1.2
docker-commons 1.3.1 (required for "sha256" prefix required in new version of docker)
Attempts to publish get:
unauthorized: authentication required
If you run docker login manually from bash and the credentials get stored in .docker/config.json then it will start working, but I will not login on it's own. I've confirmed that the username and password we have set in credentials is correct.
[JENKINS-33116] Not logging in on new slave agent in kubernetes.
| Environment | Original: Kubernetes master slave configuration. | New: Kubernetes master slave configuration. Registry is a private registry. |
| Environment | Original: Kubernetes master slave configuration. Registry is a private registry. | New: Kubernetes master slave configuration. Registry is a private registry (v2). |
| Description | Original: This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. |
New:
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. Upon futher testing, it looks like registry auth is not working at all. |
| Description |
Original:
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. Upon futher testing, it looks like registry auth is not working at all. |
New:
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. Upon further testing, it looks like registry auth is not working at all: docker-build-publish 1.2 docker-commons 1.3.1 (required for "sha256" prefix required in new version of docker) |
| Description |
Original:
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. Upon further testing, it looks like registry auth is not working at all: docker-build-publish 1.2 docker-commons 1.3.1 (required for "sha256" prefix required in new version of docker) |
New:
This plugin will not log in when a slave agent goes down and another one replaces it. You must manually bash into the agent and run "docker login" to get it to work again. Upon further testing, it looks like registry auth is not working at all: docker-build-publish 1.2 docker-commons 1.3.1 (required for "sha256" prefix required in new version of docker) Attempts to publish get: unauthorized: authentication required If you run docker login manually from bash and the credentials get stored in .docker/config.json then it will start working, but I will not login on it's own. I've confirmed that the username and password we have set in credentials is correct. |
| Workflow | Original: JNJira [ 168985 ] | New: JNJira + In-Review [ 183307 ] |
I am also hitting this issue.