jesseduffield / jesseduffield/lazydocker
Project Logs "docker-compose: command not found"
- Dominant language
- Go
- Stars
- 52.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Starting with version 0.25.0, I'm seeing `bash: line 1: docker-compose: command not found` on the Logs tab for every Project entry. I was able to downgrade to 0.24.4 and the issue goes away, so I believe this is a regression.
I don't know if it's relevant, but the way I use lazydocker involves modifying my `DOCKER_HOST` env. I'll include it in my repro steps in case it's relevant.
Steps to reproduce the behavior:
1. Have multiple containers running on a host using `docker compose run -d`.
2. On a separate machine, run `DOCKER_HOST=ssh:// lazydocker`
3. Use Shift+Tab to move to the Projects window and view their `Logs` tab.
Expected behaviour: Logs should be visible.
Desktop:
- Docker Host OS: Debian 13 (Trixie)
- Client OS: Arch
- Lazydocker Version: 0.25.0-1 (from arch `extra` repo)
Contributor guide
Research direction
Start at the Projects window's Logs tab and reproduce the failure with multiple containers, `docker compose run -d`, and `DOCKER_HOST=ssh:// lazydocker`. Trace why logs invoke `docker-compose` in this remote setup; done means Project logs are visible on version 0.25.0 without the command-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100