jesseduffield/lazydocker

Recent update of Docker seems to have broken lazydocker - MacOS X Ventura 13.4

otherwhitefrank opened this issue · 4 comments

otherwhitefrank commented

Describe the bug
Running lazydocker where it worked previously brings up following message.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Lazydocker --version

(base) frank@Franks-Mac-Studio  ~/code/b   main ±  lazydocker --version Version: 0.20.0 Date: BuildSource: homebrew Commit: OS: darwin Arch: arm64

Installed via docker .dmg, upgraded yesterday
(base) frank@Franks-Mac-Studio  ~/code/b   main ±  docker --version Docker version 24.0.2, build cb74dfc

docker-compose works fine
(base) frank@Franks-Mac-Studio  ~/code/b   main ±  docker-compose --version Docker Compose version v2.18.1

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade Docker on MacOS X to above referenced version
  2. Run 'lazydocker'

Expected behaviour
Lazydocker runs correctly

Screenshots
image

Desktop (please complete the following information):

  • OS: MacOS Ventua 13.4
  • Lazydocker Version 0.20.0 (Installed via brew)
mark2185 commented

But is the daemon running?

Can you start docker containers, pull images, and so on, from the command line? If not, try launching docker desktop and try again.

otherwhitefrank commented

Yup docker, its CLI, the docker engine GUI, and docker-compose all work

`
(base) ✘ frank@Franks-Mac-Studio  ~/code/b   main ±  docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
70f5ac315c5a: Pull complete
Digest: sha256:fc6cf906cbfa013e80938cdf0bb199fbdbb86d6e3e013783e5a766f50f5dbce0
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

  1. The Docker client contacted the Docker daemon.
  2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (arm64v8)
  3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
  4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
https://docs.docker.com/get-started/
`

similar output with my much larger docker-compose stack and running 'docker-compose up' all works fine. I was using lazydocker as a nicer interface and it broke on my last docker update and/or MacOS update (last 2-3 days)

otherwhitefrank commented

Think it may be this, looks like they moved the docker.sock to my local directory? Ran 'sudo netstat -tunl | grep docker.sock'

836ae7eac192ac27 stream      0      0 836ae7eac5eeb9b7                0                0                0 /Users/frank/.docker/run/docker.sock
otherwhitefrank commented

Was able to get it to work again with following.

export DOCKER_HOST=unix:///Users/frank/.docker/run/docker.sock

Happy to close, would recommend a warning in README or FAQ, as I think at least the MacOS Docker upgrade is moving the docker.sock around (pretty sure mine wasn't local before, as lazydocker ran fine with no explicit DOCKER_HOST set). Thanks for help.

  • 👍9