-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
No progress information while copying images to ECR #6681
Comments
Spike to reproduce on a different computer. |
@hannes-ucsc: "@dsotirho-ucsc confirms this is reproducible (Skopeo lacks progress info). @dsotirho-ucsc to investigate if Skopeo can be coaxed into providing progress information." |
This is a requested feature since May 2019 Please provide a basic progress / transfer speed output ("CI compatible") on copy |
Please consider |
Without
|
@hannes-ucsc: "It appears that skopeo detected the destination blobs to already exists, which raises doubts as to whether the deletion from ECR was effective. If it wasn't, the above terminal transcript might not correctly represent what debug output would look like when blobs are actually copied." |
See comment for revised statement
|
Assignee to revise statement in light of clarifications regarding the objective of this ticket. |
Adding the |
Assignee to implement proposed solution. |
For demo, attempt to reproduce (delete big image, taint TF resource, redeploy |
When @achave11-ucsc and I diagnosed a problem with deploying the
shared
component from his computer, we noticed that Skopeo was eerily quiet during the copy. It appeared to be hung or not make any significant progress. Either way, we need to ensure that it obvious to the user what progress Skopeo is making, or if it is making any at all.The text was updated successfully, but these errors were encountered: