One of the configured repositories failed (added from: https://download.docker.com/linux/centos/dock

[mbs@mbs01 yum.repos.d]$ yum clean all
[mbs@mbs01 ~]$ sudo yum install -y docker-ce docker-ce-cli containerd.io
Loaded plugins: fastestmirror, product-id, search-disabled-repos
Loading mirror speeds from cached hostfile
 * base: mirrors.bfsu.edu.cn
 * extras: mirrors.bfsu.edu.cn
 * updates: mirrors.ustc.edu.cn
base                                                | 3.6 kB     00:00     
docker-ce-stable                                    | 3.5 kB     00:00     
https://download.docker.com/linux/centos/docker-ce.sudo/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

 One of the configured repositories failed (added from: https://download.docker.com/linux/centos/docker-ce.sudo),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=download.docker.com_linux_centos_docker-ce.sudo ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable download.docker.com_linux_centos_docker-ce.sudo
        or
            subscription-manager repos --disable=download.docker.com_linux_centos_docker-ce.sudo

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=download.docker.com_linux_centos_docker-ce.sudo.skip_if_unavailable=true

failure: repodata/repomd.xml from download.docker.com_linux_centos_docker-ce.sudo: [Errno 256] No more mirrors to try.
https://download.docker.com/linux/centos/docker-ce.sudo/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[mbs@mbs01 ~]$ vi /etc/yum.repos.d/epel.repo

[3]+  Stopped                 vi /etc/yum.repos.d/epel.repo
[mbs@mbs01 etc]$ cd yum.repos.d/
[mbs@mbs01 yum.repos.d]$ rm -rf ./download.docker.com_linux_centos_docker-ce.sudo.repo 
rm: cannot remove ‘./download.docker.com_linux_centos_docker-ce.sudo.repo’: Permission denied
[mbs@mbs01 yum.repos.d]$ ls
CentOS-Base.repo
CentOS-CR.repo
CentOS-Debuginfo.repo
CentOS-fasttrack.repo
CentOS-Media.repo
CentOS-Sources.repo
CentOS-Vault.repo
CentOS-x86_64-kernel.repo
docker-ce.repo
download.docker.com_linux_centos_docker-ce.sudo.repo
[mbs@mbs01 yum.repos.d]$ yum clean all
Loaded plugins: fastestmirror, product-id, search-disabled-repos
Cleaning repos: base docker-ce-stable
              : download.docker.com_linux_centos_docker-ce.sudo extras
              : updates
Cleaning up list of fastest mirrors
Other repos take up 62 M of disk space (use --verbose for details)
[mbs@mbs01 yum.repos.d]$ sudo rm -rf ./download.docker.com_linux_centos_docker-ce.sudo.repo 
[sudo] password for mbs: 
[mbs@mbs01 yum.repos.d]$ ls
CentOS-Base.repo       CentOS-fasttrack.repo  CentOS-Vault.repo
CentOS-CR.repo         CentOS-Media.repo      CentOS-x86_64-kernel.repo
CentOS-Debuginfo.repo  CentOS-Sources.repo    docker-ce.repo
[mbs@mbs01 yum.repos.d]$ yum clean all
Loaded plugins: fastestmirror, product-id, search-disabled-repos
Cleaning repos: base docker-ce-stable extras updates
Other repos take up 62 M of disk space (use --verbose for details)
[mbs@mbs01 yum.repos.d]$ yum makecache
Loaded plugins: fastestmirror, product-id, search-disabled-repos
Determining fastest mirrors
 * base: mirrors.bfsu.edu.cn
 * extras: mirrors.bfsu.edu.cn
 * updates: mirrors.ustc.edu.cn
base                                                | 3.6 kB     00:00     
docker-ce-stable                                    | 3.5 kB     00:00     
extras                                              | 2.9 kB     00:00     
updates                                             | 2.9 kB     00:00     
(1/8): docker-ce-stable/7/x86_64/other_db             | 116 kB   00:01     
(2/8): extras/7/x86_64/filelists_db                   | 224 kB   00:01     
(3/8): extras/7/x86_64/other_db                       | 134 kB   00:00     
(4/8): base/7/x86_64/other_db                         | 2.6 MB   00:02     
(5/8): docker-ce-stable/7/x86_64/filelists_db         |  23 kB   00:02     
(6/8): updates/7/x86_64/filelists_db                  | 2.4 MB   00:05     
(7/8): base/7/x86_64/filelists_db                     | 7.2 MB   00:16     
(8/8): updates/7/x86_64/other_db                      | 319 kB   00:20     
Metadata Cache Created
[mbs@mbs01 yum.repos.d]$ yum update
Loaded plugins: fastestmirror, product-id, search-disabled-repos
You need to be root to perform this command.
[mbs@mbs01 yum.repos.d]$ 
 

  • 1
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
The error message "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" indicates that there is a problem connecting to the Docker daemon. The Docker daemon is responsible for managing Docker containers and must be running for Docker commands to work. In the provided references, the user encountered this issue after restarting the server, and the Docker containers were not working. They tried various solutions but were unable to resolve the problem until they manually started the Docker daemon. To fix this issue, you can try the following steps: 1. Check if the Docker daemon is running by using the command: [2] ``` systemctl status docker ``` This command will show the status of the Docker service. If it is not running, you will need to start it. 2. Start the Docker daemon by using the command: [2] ``` dockerd ``` This command will start the Docker daemon and allow you to connect to it. 3. If the above steps do not resolve the issue, you can try restarting the Docker service: [2] ``` systemctl restart docker ``` This command will restart the Docker service and may help in resolving any underlying issues. Additionally, you can use the following commands for troubleshooting: - To check the running services, you can use: [3] ``` systemctl | grep running ``` This command will show the list of running services, and you can check if the Docker service is listed. - To view the Docker service startup logs, you can use: [3] ``` journalctl -u docker ``` This command will display the logs related to the Docker service startup, which can help in identifying any errors or issues. Remember to check the system requirements and ensure that Docker is properly installed and configured on your CentOS system.<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* *2* *3* [cannot connect to the docker daemon at unix ///var/run/docker.sock. Is the docker daemon running?](https://blog.csdn.net/l751475472/article/details/122968595)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 100%"] [ .reference_list ]

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值