You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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!
docker run --pull
ensures the latest version of the image is pulled from the repository. Currently We have asarus pull
before thesarus 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.The text was updated successfully, but these errors were encountered: