run dive without sudo

[dp-anto]

When I run dive test:latest I get:

Image Source: docker://test:latest
Extracting image from docker-engine... (this can take a while for large images)
> could not determine docker host: context "default": context not found: open /home/john/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/meta.json: no such file or directory
cannot fetch image
unable to parse docker host ``

Conversely when I run it with sudo, sudo dive test:latest, it works. Is there a way to run dive without using sudo? I was expecting not to need sudo given that my user (the one that is running dive) is already associated to the docker group that is the one need to connect to the Docker daemon and the dive process should inherit my supplementary groups.

[tree-1917]

Hello Sir,
This issue is not related to Dive itself, but to the fact that your user does not have access to the Docker daemon’s Unix socket:

/var/run/docker.sock

1. Check your current groups:

groups

If you do not see the docker group listed, this is the problem.

2. Add your user to the docker group:

sudo usermod -aG docker $USER

You must logout and login again

4. After logging in again, test:

docker ps
dive test:latest

Both commands should now work without sudo.

---

[dp-anto]

@tree-1917 This is the error I get sometimes if I do not sudo:

Image Source: docker://****************
Extracting image from docker-engine... (this can take a while for large images)
could not determine docker host: context "default": context not found: open /home/John/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/meta.json: no such file or directory
cannot fetch image
unable to parse docker host ``

but if then I prepend sudo it works.

[tree-1917]

Hello @dp-anto,

can first list all current context :

docker context ls 

As your error message indicates, the default context cannot be found. If the default context does not exist, you can create it with:

docker context create default

and it should works without needing sudo.

[JoshuaRVONQ]

I have the same issue. I am able to run docker up and down as regular user. I (user) am in the docker group.

But I am unable to use the latest dive version. Keeps complaining about default context, which is there:

docker context ls
NAME        DESCRIPTION                               DOCKER ENDPOINT               ERROR
default *   Current DOCKER_HOST based configuration   unix:///var/run/docker.sock   

ls -l /var/run/docker.sock
srw-rw---- 1 root docker 0 jan  5 08:53 /var/run/docker.sock

groups
[username] adm cdrom sudo dip www-data video plugdev lpadmin sambashare docker

but the command:

dive dive:latest
Image Source: docker://dive:latest
Extracting image from docker-engine... (this can take a while for large images)
> could not determine docker host: context "default": context not found: open /home/[username]/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/meta.json: no such file or directory
cannot fetch image
unable to parse docker host

And the file /home/[username]/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/meta.json: is not there. Not sure what it should be, but it is not there

So how can we fix that a normal user can use dive again?

[egormkn]

The issue is that the default context does not have a corresponding meta.json. It was previously mentioned in the docs:

The default context behaves differently than manually created contexts. It does not have a meta.json configuration file, and it dynamically updates based on the current configuration.

Maybe for the latest docker versions this behaviour has been changed.

I've found a workaround using a manually created meta.json:

mkdir -p ~/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/
docker context inspect default | jq -c '.[0]' >~/.docker/contexts/meta/37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688f/meta.json