This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 884
--pull-policy="new" is not the default policy #3579
Comments
I added in the following line to
I then ran a couple
What behavior are you observing when you don't pass the |
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment
What did you do?
rkt run --help
tells thatpull-policy
is default value isnew
but setting it explicitly is acting differently.I'm fetching an aci file that have explicit dependencies (with version label) that I previously fetched.
When I run rkt fetch without the pull-policy, it fail because rkt is fetching image remotly, but the domain name I use do not exists.
When I run the fetch with
--pull-policy="new"
it's working.What did you expect to see?
New is the default policy.
dgr is broken because of this change.
The text was updated successfully, but these errors were encountered: