-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Unable to push to repository due to "manifest invalid" error. #10879
Comments
Following the error from Artifactory where it says the label
|
This issue has been automatically migrated to hashicorp/packer-plugin-docker#28 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-docker#28. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
Overview of the Issue
We have a number of packer configuration files (
json
), that builds a container but when we try to push to our internal registry we get an error of:docker (docker-push): manifest invalid: manifest invalid
.Reproduction Steps
Just run
packer build <gist file>
on Mac OS (Big Sur). I tried to reproduce this on Linux (Ubuntu 18.04) using Packer 1.7.2 and I could not but a coworker could reproduce this on another Mac OS (Big Sur) machiune.Packer version
Tested with Packer 1.7.2, 1.6.0, and 1.5.6.
Simplified Packer Buildfile
A sample json file has been placed here
Operating system and Environment details
Mac OS X (amd64), Big Sur (11.2.2)
Log Fragments and crash.log files
From our internal registry (Artifactory) we see this in the logs:
From the packer run we see this:
The text was updated successfully, but these errors were encountered: