Phil Estes
Phil Estes
What version of `manifest-tool` were you using? I can test this with my test GCR instance when I get a chance. If you built from `main` in the last few...
> I was using `mplatform/manifest-tool:alpine` container image Ah! This is most likely a limitation of using manifest-tool from within a container. If you installed the credential helper that is on...
Looks like this is not any issue with the credential helper anyway; I just verified/tested that there are no issues with using the GCR cred helper. This might be a...
@waddles seems reasonable to enhance the container with the cred helpers, but this issue has kind of morphed from what turns out the root cause was (looks like a `scope`...
Can you run the push with `--debug` and provide the output? It sounds like it thinks a required components of the full tree of contained images (configs, manifests, and layers)...
Hi @aamato80 have you been able to try the command with `--debug` so I can help figure out your issue?
@b-morgenthaler interesting; so the specific piece of content in the first error you included is specifically: ```json { "errors": [ { "code": "BLOB_UNKNOWN", "message": "blob unknown to registry", "detail": "sha256:f5ef2458f9f1d711e98db59f2239e1171bc9ecf2c442a068e11fc62e105d2b0c"...
> verifying that the pushed images are "existing" by calling manifest-tool inspect prior to manifest-tool push for all images. manifest-tool inspect returned no errors (see my log above in the...
Looks like it wants to use temp folders in `/var/folders/nn...`; I assume that path is not mounted in the VM?
@russau that's correct, and specifically, the reason Docker exposes a UNIX socket is that Docker's engine is built around an API, the Docker Engine API, and the Docker client is...