-
Notifications
You must be signed in to change notification settings - Fork 779
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
Docker Image Pull Progress #612
Comments
@metcalfc can you please screenshot where you weren't presented with the pull progress? |
datyona create log |
Screenshot where the pull logs are not presented. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 14 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 7 days since it was marked as "stale", we are closing this Issue. Do not hesitate to reopen it later if necessary. |
Is your feature request related to a problem? Please describe.
Sometimes when the Docker image is very large or the network is slow, its difficult to understand whats happening when its that there is an image pull thats taking a long time.
Describe the solution you'd like
Many tools show a visual progress either layer by layer, or summarized for all layers. Docker Compose for example does both:
In the screenshot above. The TUI dotted squares show total image progress. And each row shows layer progress.
Describe alternatives you've considered
Its helpful to understand that its the pull that is taking time. Because this is an area that you can decide to spend more or less time to try to make the images smaller if it always takes a long time. Or move to a different host. Understanding that also makes it clear that its not an issue with Daytona.
The text was updated successfully, but these errors were encountered: