UI Crashes After Updating to v0.24.2 on Ubuntu 24.04

[Mohabdo21]

Describe the bug
After updating to lazydocker v0.24.2, the UI renders the initial layout in the terminal but immediately crashes, making the interface completely unusable. This also affects the terminal itself - the blinking cursor disappears, and the prompt remains broken until the terminal window is closed and a new one is opened. The issue occurs consistently on both Gnome Terminal and Kitty Terminal.

To Reproduce
Steps to reproduce the behavior:

1. Install or upgrade lazydocker to v0.24.2 (e.g., via Go: go install github.com/jesseduffield/lazydocker@latest).
2. Open a terminal (Gnome Terminal or Kitty).
3. Run lazydocker.
4. Observe the layout drawing briefly, followed by a crash and the terminal prompt becoming unresponsive (no blinking cursor).

Expected behaviour
The lazydocker UI should fully render and remain interactive without crashing. The terminal prompt should not be affected after exiting or during use.

Screenshots
If applicable, add screenshots to help explain your problem.
[I can provide screenshots of the broken UI and affected terminal if requested.]

Desktop (please complete the following information):

• OS: Ubuntu 24.04.3 LTS (Kernel: 6.14.0-35-generic)
• Lazydocker Version: v0.24.2

Additional context

• Docker setup:
  • Docker version: 29.0.0
  • Docker Compose version: v2.40.3
  • Docker Buildx version: v0.30.0
  • Containerd version: v2.1.5

[cosarara]

As a workaround:

1. build lazydocker in docker from git (because the images on dockerhub are 3 years old and don't support modern docker daemons)
2. run it within docker

git clone https://github.com/jesseduffield/lazydocker.git
cd lazydocker
docker build -t lazyteam/lazydocker \
    --build-arg BUILD_DATE=`date -u +"%Y-%m-%dT%H:%M:%SZ"` \
    --build-arg VCS_REF=`git rev-parse --short HEAD` \
    --build-arg VERSION=`git describe --abbrev=0 --tag` \
    .
docker run --rm -it -v \
/var/run/docker.sock:/var/run/docker.sock \
-v /yourpath:/.config/jesseduffield/lazydocker \
lazyteam/lazydocker

[claudiocp]

Same problem here. Ubuntu 24.04.3

[gurumaxi]

Same problem here

[KevS272]

As a workaround:

1. build lazydocker in docker from git (because the images on dockerhub are 3 years old and don't support modern docker daemons)
2. run it within docker

git clone https://github.com/jesseduffield/lazydocker.git
cd lazydocker
docker build -t lazyteam/lazydocker \
    --build-arg BUILD_DATE=`date -u +"%Y-%m-%dT%H:%M:%SZ"` \
    --build-arg VCS_REF=`git rev-parse --short HEAD` \
    --build-arg VERSION=`git describe --abbrev=0 --tag` \
    .
docker run --rm -it -v \
/var/run/docker.sock:/var/run/docker.sock \
-v /yourpath:/.config/jesseduffield/lazydocker \
lazyteam/lazydocker

Tried this, but unfortunately (except omitting the lazydocker config) this doesn't solve the issue on my end 🤔
Is there any fix to be expected soon?

OS: Ubuntu 22.04
Docker: 29.0.2
Compose: 2.40.3
buildx: 0.30.0
containerd: 2.1.5

[tmkelly28]

This also happens on MacOS

Lazydocker: 0.24.2
OS: macOS Sequoia Version 15.6.1 (Apple M1 Pro)
Docker: 29.0.1
Docker compose: 2.40.3

Using iterm2

[fulvi0]

This also happens on MacOS

Lazydocker: 0.24.2 OS: macOS Sequoia Version 15.6.1 (Apple M1 Pro) Docker: 29.0.1 Docker compose: 2.40.3

Using iterm2

x2

[johnoscott]

I am having this issue on macOS also. Keyboard input not responsive. Ctrl-C doesnt work. I need to wholesale quit the Terminal app to shut it down.

[turbor]

This is on Ubuntu 22.04.5 LTS using Terminology

[SunBursts75]

the same problem

[Dunkon]

Seems similar here

OS: Ubuntu 24.04.3 LTS x86_64
Kernel: 6.11.0-1027-oem
Default ubuntu terminal and terminator

[johnoscott]

@jesseduffield this seems to be a blocker for a lot of us. Can you please fix ?

[dbburg-mc]

Also happening with arch linux with docker 29.1.1 and lazydocker lazydocker-0.24.2-1 aur package.

[jesseduffield]

I can't reproduce this on my end (mac, iterm2). Also tried to reproduce on mac kitty terminal. I assume therefore this is caused by something specific to the local environment e.g. the docker compose file in the directory, the running containers. Could somebody check if they still get the issue if e.g. they run lazydocker outside a directory with a docker-compose file, and with no containers present?