admin管理员组文章数量:1134247
The error message you're encountering during my Docker build process indicates an authentication issue with my private registry (it's Harnor):
failed to authorize: failed to fetch oauth token: unexpected status from GET request to : 400 Bad Request
my gitlab ci scripts
stage: build
image: registry.internal.amdrnn.ir/library/docker:27.4.1
services:
- name: xxx.xxx/library/docker:27.4.1-dind
alias: docker
command: ["--tls=false"] # Ensure TLS is disabled
script:
- echo "Logging into Docker Registry"
- echo $CI_REGISTRY_PASSWORD | docker login -u $CI_REGISTRY_USER --password-stdin $CI_REGISTRY
- echo "Login successful"
- echo "Waiting for Docker daemon..."
- until docker info; do sleep 3; done
- echo "Building Docker image for development"
- docker build -f ./Dockerfile -t $IMAGE_REGISTRY:$CI_COMMIT_REF_SLUG .
- docker push $IMAGE_REGISTRY:$CI_COMMIT_REF_SLUG
this my ci/cd script by gilab.
it's login successfully but when it wants to build the docker image it throws that error while it's logged in
本文标签:
版权声明:本文标题:continuous integration - failed to authorize: failed to fetch oauth token: unexpected status from Harbor docker registry: 400 Ba 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1736776311a1952358.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论