-
-
Notifications
You must be signed in to change notification settings - Fork 795
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
Ability to force pull docker_image #54
Comments
Would it make sense for this to be a different action? :force_pull vs :pull? It seems almost analogous to the :create vs :create_if_missing with some of the other resources. |
+1 to :pull vs :pull_if_missing. Abstracting the docker cli should behave like the docker cli. |
+1 to separate action On Mon, Feb 3, 2014 at 1:36 PM, Jeffrey Hulten notifications@github.comwrote:
Brian Flad |
Glad I asked! I'll work up the PR accordingly. |
@gabrtv I'd be a fan of renaming current pull action to pull_if_missing. Thanks so much and let me know if you need any help. |
My PR does the following:
@gabrtv Hope we didn't work at cross purposes. I have the okay from my boss to improve this cookbook on company time. |
I've merged #55 and released 0.28.0, which should fix this behavior. I'll create a separate issue for :build action. Feel free to create others as necessary. |
Once an image exists in the local graph, there seems to be no way to update it. It's common for an image's
:latest
tag to be updated on the registry. How can we ensure we always have the right:latest
?I have an in-progress PR that implements:
..but I wanted to get some feedback before moving forward.
The text was updated successfully, but these errors were encountered: