gpt4 book ai didi

docker - 无法通过Registry.ng.bluemix.net上的IBM Containers注册表进行身份验证

转载 作者:行者123 更新时间:2023-12-02 20:26:26 24 4
gpt4 key购买 nike

当我在Bluemix上登录IBM容器时,出现以下错误:

cf ic login
** Retrieving client certificates from IBM Containers
** Storing client certificates in /Users/triplez/.ice/certs Successfully retrieved client certificates
** Checking local docker configuration OK
** Authenticating with registry at registry.ng.bluemix.net
Could not authenticate with IBM Containers registry at registry.ng.bluemix.net
**** exit status 1
****Error response from daemon: invalid registry endpoint registry.ng.bluemix.net/v0/: unable to ping registry endpoint registry.ng.bluemix.net/v0/
v2 ping attempt failed with error: Get registry.ng.bluemix.net/v2/: dial tcp: lookup registry.ng.bluemix.net on 103.11.48.126:53: read udp 103.11.48.126:53: i/o timeout
v1 ping attempt failed with error: Get registry.ng.bluemix.net/v1/_ping: dial tcp: lookup registry.ng.bluemix.net on 103.11.48.126:53: read udp 103.11.48.126:53: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add --insecure-registry registry.ng.bluemix.net to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/registry.ng.bluemix.net/ca.crt



我已经卸载了docker并重新安装,给了我同样的错误。我还删除了 ~/.cf/config.json~/.ice/ice-cfg.ini~/.ice/certs/,然后尝试再次登录。我仍然收到相同的错误。

我也用ice cli测试了这个错误。

已编辑

尝试了以下命令:
ice login -a 'https://api.ng.bluemix.net' --registry 'registry.ng.bluemix.net' --host 'https://containers-api.ng.bluemix.net/v3/containers'

得到了同样的错误:

Authentication with container cloud service at containers-api.ng.bluemix.net/v3/containers completed successfully You can issue commands now to the container service

Proceeding to authenticate with the container cloud registry at registry.ng.bluemix.net/v3 Error response from daemon: invalid registry endpoint registry.ng.bluemix.net/v3/v0/: unable to ping registry endpoint registry.ng.bluemix.net/v3/v0/

v2 ping attempt failed with error: Get registry.ng.bluemix.net/v3/v2/: dial tcp: lookup registry.ng.bluemix.net on 192.168.0.1:53: read ump 192.168.0.1:53: i/o timeout
v1 ping attempt failed with error: Get registry.ng.bluemix.net/v3/v1/_ping: dial tcp: lookup registry.ng.bluemix.net on 192.168.0.1:53: read udp 192.168.0.1:53: i/o timeout. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add --insecure-registry registry.ng.bluemix.net to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/registry.ng.bluemix.net/ca.crt

docker is not available on your system or is not properly configured

Could not authenticate with cloud registry at registry.ng.bluemix.net/v3

You can still use IBM Containers but will not be able to run local docker containers, push, or pull images

最佳答案

容器云服务主机名似乎不正确。
请尝试运行ice登录命令,如下所示:

ice login -a 'https://api.ng.bluemix.net' --registry 'registry.ng.bluemix.net' --host 'https://containers-api.ng.bluemix.net/v3/containers'

关于docker - 无法通过Registry.ng.bluemix.net上的IBM Containers注册表进行身份验证,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/32449518/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com