rkt: Image pull policy of 'Always' is not respected #27646
Assignees
Labels
Comments
yifan-gu
changed the title
k8s-github-robot
pushed a commit
that referenced
this issue
Aug 26, 2016
Automatic merge from submit-queue rkt: Force `rkt fetch` to fetch from remote to conform the image pull policy. Fix #27646 Use `--no-store` option for `rkt fetch` to force it to fetch from remote. However, `--no-store` will fetch the remote image regardless of whether the content of the image has changed or not. This causes performance downgrade when the image tag is ':latest' and the image pull policy is 'always'. The issue is tracked in rkt/rkt#2937.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setting a pull policy of
Alwaysshould cause the runtime to always hit the remote server for an image. However, therkt fetchinvocation used to get the image always checks the cache first, rather than hit the network.This also impacts
AlwaysPullPolocies that are implicitly added to:latesttagged images.The impact of this is that a ":latest" tagged image will not be updated on each new run under rktnetes, unless it has been removed. Similarly, when setting a global pull policy of
Always, the image will not be updated unless removed.cc @kubernetes/sig-rktnetes
The text was updated successfully, but these errors were encountered: