Unable to push image to built in repository

[JackInTheBoxBen]

Summary

When pushing an image to the built in repository I get the following error: received unexpected HTTP status: 500 Internal Server Error When pulling an image from the build in repository I get the following error: Error response from daemon: manifest for 172.30.0.178:32000/employmentwebapiqueries:latest not found: manifest unknown: manifest unknown

What Should Happen Instead?

The image should be able to be pushed or pulled to the built in repository

Reproduction Steps

Yes I am able to reproduce even on simple images like docker Hello-World.

1. Tag image with ip address from multipass and port 32000
2. push image using docker Note insecure registry is set in docker daemon using the multipass ip address and port 32000

1. ...
2. ...

Introspection Report

Can you suggest a fix?

This looks like this some kind of issue with the manifest not being able to be added to the repository. Deployment is also failing because it cannot find the image in the repo.

Are you interested in contributing with a fix?

[JackInTheBoxBen]

This is from the container-registry node pod logs when pushing the Docker Hello-World container

microk8sregistryerror.txt

[JackInTheBoxBen]

I think the issue is this when trying to put the manifest out there it is using port 45887 for some reason and not port 32000. This works http://172.22.46.115:32000/v2/employmentwebapiqueries/manifests/1.0.0 when accessing with a browser. This does not work http://172.22.46.115:45887/v2/employmentwebapiqueries/manifests/1.0.0 when accessing the failing url with a browser. Is this the proper forum for add on issues or do I need to report the issue to whoever maintains the repository add on?

[JackInTheBoxBen]

Found the issue. Besides insecure registries the following json needs to be added to the docker daemon.json file "allow-nondistributable-artifacts": [ "youripaddress:32000" ] Leaving this issue open as this should probably be added to the microk8s documentation?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.