-
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." |
The
are printed the same and in the same frequency with or without The additional debug lines that are printed mostly relate to internal processes between image uploads (e.g. connection setup, checking if the destination already exists). There is a potentially useful debug line mentioning the completion of a blob's upload, however a single image can consist of many blobs (10 for the kibana image), and the increased number of log lines printed with debug enabled, 34 vs 242 for one (kibana) image, make finding all the blobs relating to one image not easy to obtain. Example: logs relating to one blob's upload (note last line "Upload of layer ... complete")
|
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: