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
v4.3.7
执行命令: [root@master sealos4.4.0]# sealos registry copy reg.ide.local:5000/titanide/busybox:latest sealos.hub:5000 Getting image source signatures Error: trying to reuse blob sha256:5cc84ad355aaa64f46ea9c7bbcc319a9d808ab15088a27209c9e70ef86e5a2aa at destination: checking whether a blob sha256:5cc84ad355aaa64f46ea9c7bbcc319a9d808ab15088a27209c9e70ef86e5a2aa exists in sealos.hub:5000/titanide/busybox: authentication required
No response
- Sealos version: - Docker version: - Kubernetes version: - Operating system: - Runtime environment: - Cluster size: - Additional information:
The text was updated successfully, but these errors were encountered:
两个镜像仓库都要login吧
Sorry, something went wrong.
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
You need to log in to both mirror repositories.
尝试过不行
Tried but it doesn’t work
This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.
No branches or pull requests
Sealos Version
v4.3.7
How to reproduce the bug?
执行命令:
[root@master sealos4.4.0]# sealos registry copy reg.ide.local:5000/titanide/busybox:latest sealos.hub:5000
Getting image source signatures
Error: trying to reuse blob sha256:5cc84ad355aaa64f46ea9c7bbcc319a9d808ab15088a27209c9e70ef86e5a2aa at destination: checking whether a blob sha256:5cc84ad355aaa64f46ea9c7bbcc319a9d808ab15088a27209c9e70ef86e5a2aa exists in sealos.hub:5000/titanide/busybox: authentication required
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
Additional information
No response
The text was updated successfully, but these errors were encountered: