没有不值得去解决的问题,也没有不值得去学习的技术!

How to Resolve “repository not found: does not exist or no pull access” When Building Images in Jenkins

When building the image in Jenkins, an error occurs: repository registry-vpc.cn-beijing.aliyuncs.com/cmc/centos-nginx112-php72 not found: does not exist or no pull access.

1. When building the image in Jenkins, an error occurs: repository registry-vpc.cn-beijing.aliyuncs.com/cmc/centos-nginx112-php72 not found: does not exist or no pull access. See Figure 1.

When building the image in Jenkins, an error occurs: repository registry-vpc.cn-beijing.aliyuncs.com/cmc/centos-nginx112-php72 not found: does not exist or no pull access.
Figure 1
Dockerfile

RUN chown -R nginx:nginx /mcloud/www/ && \
    rm -rf /etc/nginx/conf.d/status.conf && \
    chmod +x /usr/local/bin/composer && \
    composer config -g repo.packagist composer https://mirrors.aliyun.com/composer/ && \
    cd /mcloud/www/cmcp-api && \
    composer install

2. Adjust the configuration options under Build – Execute shell – Command; the username and password values need to be modified. See Figure 2.

Adjust the configuration options under Build - Execute shell - Command; the username and password values need to be modified.
Figure 2
Bash

#!/bin/bash
docker login --username= --password= registry-vpc.cn-beijing.aliyuncs.com

3. Build again, and the build succeeds. See Figure 3.

Build again, and the build succeeds.
Figure 3

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系