We recently forked the Docker plugin to add some extra labels that are useful for us when tracking code changes across our Ci/CD pipeline. When changing one of our builds to use the new image, authentication is failing when it was previously working with
plugins/docker. I’ve added our new image to the Secret as allowed but we’re still seeing the authentication failure.
Is there anything else I need to do to allow Secrets to be passed into custom plugin images?
I’ve configured our publish step like this:
publish: image: our-custom-image secrets: [docker_username, docker_password] registry: quay.io repo: quay.io/our-project tags: - latest
I’ve verified that the username/password that I’m using is valid and we have other projects using
plugin/docker with the same credentials.