Dive always fail when trying to fetch local image

Question

Dive always fail when trying to fetch local image

joaocasarin opened this issue a year ago · 9 comments

I have a local image called jcasarin:t with id d18bf00f8397. When I run dive d18bf00f8397 or dive jcasarin:t it always fail with the following response:

Image Source: docker://d18bf00f8397
Fetching image... (this can take a while for large images)
Handler not available locally. Trying to pull 'd18bf00f8397'...
Using default tag: latest

Error response from daemon: pull access denied for d18bf00f8397, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
cannot fetch image
exit status 1

Although fetching image doesn't necessarily means it is pulling from docker hub, it does seem to be trying to do that.

I have already ran docker login docker.io and also docker login <my_company_docker_registry> and both are already authenticated, but still get that deny error.

PS.: I did not push the image to any registry, it is just local!

Answer 1 · 2023-07-13T06:10:44.000Z

Handler not available locally. Trying to pull 'd18bf00f8397'...
Using default tag: latest

This means it will try to pull an image named d18bf00f8397 with the tag latest which is not what you want.

Could you please post the output of docker images | grep jcasarin and dive jcasarin:t?

Also, which version of dive are you using?

Answer 2 · 2023-07-13T17:45:41.000Z

Hi @mark2185 ,
as requested this is the output of the first command:

second command:

dive version: dive 0.10.0

Answer 3 · 2023-07-17T16:28:03.000Z

I suspect this is the same issue resolved by #453 (comment) . It happens when newer versions of Docker Desktop are installed without admin privileges on macOS.

Answer 4 · 2023-07-17T17:49:58.000Z

@jmbowman interesting, perhaps it has something to do with the docker client I am using then. We are not allowed to use Docker Desktop so we have an internal docker client, may that be the cause?

Answer 5 · 2023-07-25T09:13:23.000Z

maybe also related to: #452

Answer 6 · 2023-08-02T08:52:05.000Z

I have the same issue on macOS. Using colima as docker engine. Dive tries to pull the image (and fails) while it's just available locally.

Answer 7 · 2023-08-02T20:45:46.000Z

Hi,
just wanted to share here I found the solution for our internal tool.
We needed to export following environment variables:

DOCKER_CERT_PATH=$(docker context inspect -f '{{ .Storage.TLSPath }}/docker')
DOCKER_HOST=$(docker context inspect -f '{{ .Endpoints.docker.Host }}')
DOCKER_TLS_VERIFY=1
export DOCKER_CERT_PATH DOCKER_HOST DOCKER_TLS_VERIFY

After doing that, I could use dive as usual in the current terminal session.

maybe you want to take a look about these variables with the dev of colima, @joske ?

Answer 8 · 2023-10-03T12:21:48.000Z

maybe you want to take a look about these variables with the dev of colima, @joske ?

Hi @joaocasarin, I am using colima too and just found I have the same problem. Are you saying I should export those variables and see if this works for colima as well? Thanks!

EDIT: I tried this and this is the error that was raised:

Image Source: docker://omi-kml
Fetching image... (this can take a while for large images)
cannot fetch image
could not read CA certificate "/Users/luca/.docker/contexts/tls/f24fd3749c1368328e2b149bec149cb6795619f244c5b584e844961215dadd16/docker/ca.pem": open /Users/luca/.docker/contexts/tls/f24fd3749c1368328e2b149bec149cb6795619f244c5b584e844
961215dadd16/docker/ca.pem: no such file or directory

I am not sure where colima stores the certificates..

Answer 9 · 2023-10-06T17:51:20.000Z

maybe you want to take a look about these variables with the dev of colima, @joske ?

Hi @joaocasarin, I am using colima too and just found I have the same problem. Are you saying I should export those variables and see if this works for colima as well? Thanks!

EDIT: I tried this and this is the error that was raised:
Image Source: docker://omi-kml
Fetching image... (this can take a while for large images)
cannot fetch image
could not read CA certificate "/Users/luca/.docker/contexts/tls/f24fd3749c1368328e2b149bec149cb6795619f244c5b584e844961215dadd16/docker/ca.pem": open /Users/luca/.docker/contexts/tls/f24fd3749c1368328e2b149bec149cb6795619f244c5b584e844
961215dadd16/docker/ca.pem: no such file or directory
I am not sure where colima stores the certificates..

Hi, actually I use our own internal implementation of docker engine, not Colima. I was told about those variables so we could use Dive, but probably the developers of Colima should know better what to do in order to get it working as well...

Perhaps you open an issue on Colima's repo and mention this thread?