Skip to content
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

[Discussion] Lazy pulling additonal flags #716

Closed
catric333 opened this issue Mar 28, 2022 · 2 comments
Closed

[Discussion] Lazy pulling additonal flags #716

catric333 opened this issue Mar 28, 2022 · 2 comments

Comments

@catric333
Copy link

Hi,

I was wondering if stargz-snapshotter can be configured to pull the entire image after what was required for the container to start is pulled. Let's say I'm trying to start a container with a estargz image, start it, but then would like to eventually have the whole image present after the container has already started with the minimal chunks of the image present. This way I would be safe in the event that the registry goes down and some other part of the container image would attempt to be pulled and fail.

Would this be an option I can enable? Or does this happen by default? I was trying to dig through documentation and didn't find an answer that gave me 100% certainty.

Thanks!

@ktock
Copy link
Member

ktock commented Mar 29, 2022

@catric96

pull the entire image after what was required for the container to start is pulled.

Yes, this is the default behaviour.
You can monitor the status of pulling at /.stargz-snapshotter in the container: https://github.com/containerd/stargz-snapshotter/blob/v0.11.3/docs/overview.md#state-directory

@ktock
Copy link
Member

ktock commented Mar 29, 2022

Closing this because this is answered by #716 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants