You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
From our internal registry (Artifactory) we see this in the logs:
2021-04-07T12:04:18.575Z [jfrt ] [WARN ] [7b02eb14f7c5ddb6] [.r.ArtifactoryResponseBase:125] [-nio-8081-exec-14780] - Sending HTTP error code 400: Property key: docker.label.desktop.docker.io/binds/0/SourceKind is invalid due to Name must start with a letter and cannot contain whitespace or special characters
2021-04-07T12:04:18.577Z [jfrt ] [ERROR] [7b02eb14f7c5ddb6] [h.DockerManifestPutHandler:261] [-nio-8081-exec-14780] - Error uploading manifest: 'Property key: docker.label.desktop.docker.io/binds/0/SourceKind is invalid due to Name must start with a letter and cannot contain whitespace or special characters'
This issue was originally opened by @madelaney as hashicorp/packer#10879. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
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: