Closed MiRaIOMeZaSu closed 1 year ago
Neither manifest-tool
nor docker mainfest
worked well, and I tried podman manifest
, everything solved.
I have the same problem with Nexus. Has anyone been able to use this tool with the Nexus container registry?
I have nexus docker registry and it does support
docker manifest-v2-2
as well asoci image index
(which I have tried with buildx). But while I was going to push index with manifest-tool, it did't work. The YAML file is as follow:and it failed with
FATA[0000] Error pushing manifest list/index to registry: sha256:273426f6391efb54d55c809383f7403cecf8f6fec220299d9bbaf2edbc0f4437: manifest list/index references to blobs and/or manifests are missing in your target registry: failed commit on ref "index-hub.mynexusdomain.com/mirai0/mysql-multiarch:5.7@sha256:273426f6391efb54d55c809383f7403cecf8f6fec220299d9bbaf2edbc0f4437": unexpected status: 400 Bad Request
I notice a prefix "index-" was add to my registry host, buthub.mynexusdomain.com
is the only domain I expose for accepting request path start with/v2/
. Then I try it with hub.docker.com and it works fine with below:I thought the "index-" prefix was for hub.docker.com and then I try with ip+port, I add registry to docker Insecure Registries and change the YAML file to:
But manifest did't seem to use Insecure Registries config with following error output:
And I don't know what I could do to solve this, so please help.