happy-pizza-3050711/17/2021, 8:00 AM
returned an error "_denied: requested access to the resource is denied_" from docker-cli. Meanwhile a plain
worked just fine. My Jenkinsfile wraps the
step inside withDockerRegistry. The urls specified in withDockerRegistry and in
are identical (though Pipeline plugin requires a protocol prefix whereas pants doesn't). In our Pipeline, we use a separate credentials to login and push the image and that account is different from the pipeline runner, i.e.
. The last thing worth mentioning is that the docker images were built prior to entering withDockerRegistry, meaning that they were built under the name of
. Am I doing something wrong perhaps?
curved-television-656811/17/2021, 8:09 AM
properly. This may very well be a bug in our docker backend. I’ll investigate further, but it’ll be some time..
works when running from the command line. (with properly setup here, I refer to there being a successfully issued
./pants publish <docker-image>
for the registry you want to push to.) I’ve not had the opportunity to test running a Jenkins pipeline with the docker plugin you mention, but it feels like it could be in proximity there abouts. It should not matter which user built the image, however.
Meanwhile a plainWas this also executed from within theworked just fine.
happy-pizza-3050711/18/2021, 7:57 AM
curved-television-656811/18/2021, 1:45 PM
happy-pizza-3050711/18/2021, 3:09 PM
curved-television-656811/18/2021, 3:20 PM
but it should be (that was my intention, overlooked). Will fix, sorry for the trouble.
for a commit from
, after it’s been merged)
happy-pizza-3050711/18/2021, 8:47 PM
curved-television-656811/19/2021, 6:16 AM
happy-pizza-3050711/21/2021, 10:12 AM
curved-television-656811/21/2021, 10:53 AM