Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL container logs not displayed #170

Open
Tset-Noitamotua opened this issue Sep 11, 2019 · 10 comments
Open

PostgreSQL container logs not displayed #170

Tset-Noitamotua opened this issue Sep 11, 2019 · 10 comments
Labels
bug Something isn't working docker-image Docker image

Comments

@Tset-Noitamotua
Copy link

Tset-Noitamotua commented Sep 11, 2019

Describe the bug
Logs of a customized PostgreSQL container I use are not displayed

To Reproduce
Steps to reproduce the behavior:

  1. docker run --name ehrdb -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -d -p 5432:5432 rippleosi/ethercis-database-docker
  2. start lazydocker as container
  3. check Logs of ehrdb container - they are empy

Expected behaviour
Expected to see same logs that I get from following command

> docker container logs ehrdb 

# example output
2019-09-11 06:27:48.178 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2019-09-11 06:27:48.178 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2019-09-11 06:27:48.180 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-09-11 06:27:48.191 UTC [18] LOG:  database system was shut down at 2018-10-24 08:54:17 UTC
2019-09-11 06:27:48.193 UTC [1] LOG:  database system is ready to accept connections

Screenshots
image

Desktop (please complete the following information):

  • OS: Linux (Deepin 15.11 - kernel 5.0)
  • Lazydocker Version v0.7.4

Additional context
I Also tried starting ehrdb container from a customcommand for images from inside lazydocker, same behavior as described above.

@Tset-Noitamotua Tset-Noitamotua added the bug Something isn't working label Sep 11, 2019
@mjarkk
Copy link
Contributor

mjarkk commented Sep 11, 2019

Does this happen with other contains too?

@dawidd6
Copy link
Collaborator

dawidd6 commented Sep 11, 2019

Running lazydocker in Docker container won't give you logs or CPU usage. Known bug.

@dawidd6 dawidd6 added the docker-image Docker image label Sep 11, 2019
@mjarkk
Copy link
Contributor

mjarkk commented Sep 11, 2019

@dawidd6 Is this just impossible due to files outside of the docker container?
Because if so we could better just remove this logs tab from the docker container.

@dawidd6
Copy link
Collaborator

dawidd6 commented Sep 11, 2019

Honestly I have no idea why it does not work in Docker. We have docker binary in image and yet it refuses to show logs, but other stuff is working.

@mjarkk
Copy link
Contributor

mjarkk commented Sep 11, 2019

Ow i see this is indeed wired,
when i run docker:dind with the docker sock mounted it shows the logs just fine.

docker run \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -it --rm docker:dind sh

/ # docker logs redis

@dawidd6
Copy link
Collaborator

dawidd6 commented Sep 11, 2019

Yep, docker will show logs, but lazydocker not. Guess it becomes lazier in Docker.

@Tset-Noitamotua
Copy link
Author

Running lazydocker in Docker container won't give you logs or CPU usage. Known bug.

confirm, running "normally" installed lazydocker displays logs as expected

image

@dawidd6
Copy link
Collaborator

dawidd6 commented Sep 11, 2019

Added a notice about this: ef1b2b5

@facorazza
Copy link

Any news about why this happens?

@jschneekloth
Copy link

Any progress on this front? This is sort of a blocker for docker installations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working docker-image Docker image
Projects
None yet
Development

No branches or pull requests

5 participants