Empty logs

[Alexandrsv]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. open lazydocker
2. Click on container
3. Log is empty

Screenshots

Screen

Desktop (please complete the following information):

• OS: Ubuntu 24.04 LTS
• Lazydocker Version 0.23.3

Additional context
Docker version 27.1.1, build 6312585
Containers are started using the command "docker compose -f 'path' up -d"

[Brenex]

Also experiencing this issue. Using the run command line as an alias under debian:

alias lzd='docker run --rm -it --name lazydocker -v /var/run/docker.sock:/var/run/docker.sock -v ~/docker-apps/lazydocker:/.config/jesseduffield/lazydocker lazyteam/lazydocker'

Using a master compose file with docker compose up -d

[slipperybeluga]

Common thread here seems to be using docker-compose -f.

Lazydocker was working fine for me when I previously ran docker-compose up -d in my directory with a single docker-compose.yml file. Logs stopped showing up in lazydocker as I started using additional separate docker-compose files all started with -f {path} arguments.

e.g., docker-compose $(for file in /path/*.yml; do echo -n "-f $file "; done) up -d

[zouloux]

Same here, containers started with docker compose -f have empty logs. Logs are visible with docker logs $id --follow. Debian 12, lazydocker installed with curl. Version 12.3. It was working in the previous version I had but I lost the specific version number.

[zouloux]

Tested with 12.1, same issue.

[RaymondBakker]

See #391 (comment)

[Xerxes004]

See #391 (comment)

I don't think this is the same issue. I just started the service with docker compose up -d and saw no logs.

[sequencerr]

I don't see logs with bash alias approach(lazydocker the docker image), but it works with manually installed binary