Docker: Pulling images from private registry

[Diego Spinola]

Hey there folks,

 

I've been using a private registry (no https , already added it  to "/etc/docker/daemon.json" as an insecure-registries entry) to pull images to several machines in my network (most of them running ubuntu) and it works great...

 

however whenever I try to pull an image to the unraid server I get the following:
 

root@arda:~# docker -v
Docker version 18.09.6, build 481bc77
root@arda:~# docker pull "localhost:5000/mynamespace/test:latest" 
latest: Pulling from mynamespace/test
7413c47ba209: Downloading 
0fe7e7cbb2e8: Downloading 
1d425c982345: Downloading 
344da5c95cec: Downloading 
0a8244e1fdbf: Download complete 
unknown blob

Does anyone have any idea/hint of what might be going on here? if i pull the same test image elsewhere (any of my other machines) it works fine...

Thanks

Edited August 8, 2019 by Diego Spinola
removing identifiable info

[Diego Spinola]

Ok , something very weird happened:

• I pulled the image on one of the machines that were working fine with
• Ran it and created a small file in it (just a "touch" to change it's hash)
• Then committed the container to mynamespace/test:latest and pushed it to my registry
• tried to pull it again on unraid CLI:

 docker pull localhost:5000/mynamespace/test
Using default tag: latest
latest: Pulling from mynamespace/test
7413c47ba209: Pull complete 
0fe7e7cbb2e8: Pull complete 
1d425c982345: Pull complete 
344da5c95cec: Pull complete 
0a8244e1fdbf: Pull complete 
9af8d374b4e3: Pull complete 
Digest: sha256:ba9e72e1b975455825376c5b0edebbbd4e6b74d21968dc4f5e08f9bc10292c44
Status: Downloaded newer image for localhost:5000/mynamespace/test:latest

I've no idea why this works now, will try to replicate the initial conditions

Edited August 8, 2019 by Diego Spinola
removing server info