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

sarus run --pull #6

Open
jdahm opened this issue Mar 16, 2020 · 2 comments
Open

sarus run --pull #6

jdahm opened this issue Mar 16, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@jdahm
Copy link

jdahm commented Mar 16, 2020

docker run --pull ensures the latest version of the image is pulled from the repository. Currently We have a sarus pull before the sarus run invocation, but this takes 30s-1min each time building a new squashfs image. Is it possible to not incur this cost on each run but yet ensure we have the latest image? If so, I suggest adding this as a --pull to mimic the docker interface.

@rukkal rukkal added the enhancement New feature or request label Mar 17, 2020
@Madeeks
Copy link
Member

Madeeks commented Apr 6, 2020

Hello @jdahm, thank you for your suggestion.
If sarus pull only performed the pull process if the image on the remote registry changed, therefore eliminating the current overhead when the image is already up-to-date, would that be enough for your use case?
Or you would still prefer to have sarus run --pull for a one-line command?

@jdahm
Copy link
Author

jdahm commented Apr 28, 2020

If sarus pull only performed the pull process if the image on the remote registry changed, therefore eliminating the current overhead when the image is already up-to-date, would that be enough for your use case?

@Madeeks Thanks for the suggestion. Yes, this would be sufficient!

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

No branches or pull requests

3 participants