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

Option force seems to not being used when tagging docker images. #2362

Closed
hanshasselberg opened this issue Jun 30, 2015 · 3 comments
Closed
Labels
enhancement post-processor/docker pre-1.0 wontfix Out of scope/alignment with the project, or issue is expected, intended behavior

Comments

@hanshasselberg
Copy link
Member

This is what I get when I try to tag an image with an existing tag:

$ packer build -force template.json
* Post-processor failed: Error tagging image: exit status 1
Stderr: Error response from daemon: Conflict: Tag latest is already set to image a0e3da923c43e27477f0b9dd213fb508385294eb9067aab9e95e66e8fcae23a5, if you want to replace it, please use -f option

I started digging around, so far I didn't found the issue yet.

@mitchellh
Copy link
Contributor

Strange from #2055, this is just a separate configuration. We can make it work with the -force flag as well though.

@hanshasselberg
Copy link
Member Author

thanks for the pointer. because of the lack of docs I didn't expect to work that way.

@hanshasselberg
Copy link
Member Author

I would be fine with closing this issue.

@mwhooker mwhooker added pre-1.0 wontfix Out of scope/alignment with the project, or issue is expected, intended behavior labels Nov 17, 2016
@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement post-processor/docker pre-1.0 wontfix Out of scope/alignment with the project, or issue is expected, intended behavior
Projects
None yet
Development

No branches or pull requests

3 participants