When utilizing a local docker registry as part of your DKP deployment, there is a step where you can utilize the DKP binary to seed images to your local registry:
./dkp push image-bundle --image-bundle ./dkp-v2.5.1/container-images/konvoy-image-bundle-v2.5.1.tar --to-registry $DOCKER_REGISTRY_ADDRESS
While seeding you may see error messages such as the following:
2023/09/12 20:01:18 retrying without mount: POST https://harbor-registry.daclusta/v2/harbor-registry/mesosphere/kube-proxy/blobs/uploads/?from=mesosphere%2Fkube-proxy&mount=sha256%3A9fd5070b83085808ed850ff84acc98a116e839cd5dcfefa12f2906b7d9c6e50d&origin=REDACTED: UNAUTHORIZED: project not found, name: mesosphere: project not found, name: mesosphere
This appears to indicate that the image was not successfully pushed to your Harbor docker registry, but it is a false positive error message. This will only affect version of the DKP binary newer than DKP 2.4.0. This does not affect any other Local Registry solution such as Nexus or Artifactory. You can safely ignore these error messages.
To determine if you are using a DKP binary affected by this issue, run the ./dkp version command:
[tony@rockyadmin cluster-a-ag]$ ./dkp version diagnose: v0.6.3 dkp: v2.5.1 kommander: v2.5.1 konvoy: v2.5.1 mindthegap: v1.6.1
We can see above that the DKP version is higher than 2.4.0, so this binary will produce the error as expected. If you see errors similar to this on a DKP binary 2.4.0 or lower, please reach out to support as this would indicate there is a different issue that needs to be resolved.
A future version of DKP will provide a resolution to this issue and we will update this KB article at that time.