[docker-registry] Error response from daemon: unknown image in /v1.41/images/create?fromImage=

budarin · November 2, 2022, 12:15pm

After upgrading to the latest version of docker desktop, docker-registry v2 stops working properly
Have pushed the image in the registry

try to pull it

$ docker pull localhost:4000/raketa/service
Using default tag: latest
Error response from daemon: unknown image in /v1.41/images/create?fromImage=localhost%3A4000%2Fraketa%2Fservice&tag=latest

sb00020 · November 2, 2022, 9:46pm

This seems to be a bug on engine 20.10.20. I have emailed support with similar details, and had a less than helpful response. The issue is not present on 20.10.16.

It appears to be to do with the “nested” naming. For example, “docker pull server:8042/alpine:3.16.2” works fine, but “docker pull server:8042/bitnami/redis” fails on 20.10.20, but works on 20.10.16.

Edit, for completion, this also appears to be an issue on Mac

budarin · November 2, 2022, 11:44pm

I’m confused by the url - /v1.41/…
Why not /v2/ ?

I gave an example with one image, but none of the other images are loaded from the registry either

On Mac everything works well - there was no an update yet

sb00020 · November 3, 2022, 10:05am

I would suggest checking the engine version number. I just rolled back from 20.10.20 to 20.10.17 and it all works again.

By “nested” I didn’t mean it contained multiple images, I’m not sure on the correct terminology. For your example, if the service was stored directly as “localhost:4000/service” I believe it would work, but adding “raketa/service” it will break.

hackerman0 · November 3, 2022, 9:43pm

I suspect I’m running into the same root issue here with postgres:14.4 (on Windows 11)

It was working yesterday and then today my Docker Desktop updated to 4.13.1 and it broke.

fwiw I can also confirm that rollback to 4.12.0 does fix it by bringing the engine version back down with it.
also fwiw It doesn’t happen if I switch it to postgres:latest but it will happen for other tags like postgres:14.5 etc

rimelek · November 5, 2022, 8:32pm

I could reproduce the issue on my Mac. I works with any Docker version if I run Docker CE in a multipass virtual machine, but I could not pull the image called “localhost:4000/owner/myimage”, although I could push it.

It looks like it is indeed a bug in Docker Desktop and the request does not even reach the endpoint. I have tried it by running a simple HTTP server and trying to pull from and push to the HTTP server. It would not have worked obviously, but I could see the access logs. When I pished an image, I saw the access log, when I pulled the image, I didn’t see anything in the logs.

Then I tried the same in my multipass virtual machine with the same Docker CE version and I could always see something in the logs.

I am going to look for a similar issue on GitHub and report it if I can’t find any. Either way, I will get back to you with a link to an issue soon.

I could pull that image on my Mac, but there is a similar issue on GitHub. (for Mac) in Docker Desktop 4.13.0

It is stil not the link I promised

rimelek · November 5, 2022, 9:57pm

Here is the link I promised. I created a new issue.

github.com/docker/for-mac

"Error response from daemon: unknown image" when pulling an image from local registry and the tag contains the "owner" part

opened 09:55PM - 05 Nov 22 UTC

rimelek

- [x] I have tried with the latest version of Docker Desktop - [x] I have tri…ed disabling enabled experimental features - [ ] I have uploaded Diagnostics - Diagnostics ID: ### Expected behavior The following command should work with Docker Desktop in case of local registry as it works on Linux with Docker CE ``` docker pull localhost:4000/owner/myimage ``` ### Actual behavior It returns an error: ``` Using default tag: latest Error response from daemon: unknown image in /v1.41/images/create?fromImage=localhost%3A4000%2Fowner%2Fmyimage&tag=latest ``` ### Information  - macOS Version: Ventura 13.0 - Intel chip or Apple chip: Apple - Docker Desktop Version: 4.13.1 The bug is always reproducable on my Mac and it happaned to others as well on the Docker Forum: https://forums.docker.com/t/docker-registry-error-response-from-daemon-unknown-image-in-v1-41-images-create-fromimage/130944/6 I found a similar issue which was also mentioned in the same topic, but I created this isue since I could not reproduce the other one: https://github.com/docker/for-mac/issues/6540 It happens only with Docker Desktop, but not (at least for me) in a Linux virtual machine running the same Docker CE version (`20.10.20`) I also tried to run an HTTP server on the same port and see if there is any access log when I try to pull or push something (obviously I did not expect it to work) and when I did it on Linux using Docker CE, I got access logs. When I did it on Mac using Docker Desktop, I only got access logs when I pushed the image, not when I pulled. ### Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check` ``` Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0012: is the VM networking working? [SKIP] DD0030: is the image access management authorized? [PASS] DD0019: is the com.docker.vmnetd process responding? [PASS] DD0033: does the host have Internet access? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? No fatal errors detected. ``` ### Steps to reproduce the behavior  1. Go to https://docs.docker.com/registry/deploying/ 2. Run: ```bash docker run -d -p 4000:5000 --restart=always --name registry registry:2 ``` 3. Configure the Docker Engine to accept the insecure registry ```json { "insecure-registries": ["localhost:4000"] } ``` 4. Pull (for example) `ubuntu:20.04` from Docker Hub ```bash docker pull ubuntu:20.04 ``` 5. Retag the image: ```bash docker tag ubuntu:20.04 localhost:4000/owner/myimage ``` 6. Push the image ```bash docker push localhost:4000/owner/myimage ``` 7. Try to pull the image you just pushed ```bash docker pull localhost:4000/owner/myimage ``` You can try the same steps using an other image name without the "owner" part and that will work.

I also referred to the other issue with postgres mentioning that I could not reproduce that but seems similar.

hackerman0 · December 8, 2022, 12:12am

seems Docker Desktop 4.15.0 has fixed the issue. From the release notes:

Fixed regressions when parsing image references on pull. Fixes docker/for-win#13053, docker/for-mac#6560, and …(second mac issue link truncated because the forum won’t let me include more than two links ).

See full 4.15.0 release notes for more details (I would include the link but, again, the forum won’t let me include more than two links ) .