We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
描述Bug pull 报错
如何复现 请说明如何复现Bug:
预期行为 预期pull成功
截图
运行环境:
补充信息 /usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 2 is no longer
supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next
release. from cryptography.hazmat.backends import default_backend Pulling viper ... error
ERROR: for viper Get https://registry.cn-shenzhen.aliyuncs.com/v2/: dial tcp 47.107.215.73:443: connect: no route to host ERROR: Get https://registry.cn-shenzhen.aliyuncs.com/v2/: dial tcp 47.107.215.73:443: connect: no route to host @FunnyWolf
The text was updated successfully, but these errors were encountered:
https://www.yuque.com/vipersec/faq/ag9xiv
Sorry, something went wrong.
单独请求https://registry.cn-shenzhen.aliyuncs.com/v2/ 收到这样的返回,这个镜像资源是不是要登录啊? {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}
viper镜像是公开的,不需要登录,单独访问接口是要登录的
FunnyWolf
No branches or pull requests
描述Bug
pull 报错
如何复现
请说明如何复现Bug:
预期行为
预期pull成功
截图
运行环境:
补充信息
/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 2 is no longer
supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next
release.
from cryptography.hazmat.backends import default_backend
Pulling viper ... error
ERROR: for viper Get https://registry.cn-shenzhen.aliyuncs.com/v2/: dial tcp 47.107.215.73:443: connect: no route to host
ERROR: Get https://registry.cn-shenzhen.aliyuncs.com/v2/: dial tcp 47.107.215.73:443: connect: no route to host
@FunnyWolf
The text was updated successfully, but these errors were encountered: