jesseduffield / jesseduffield/lazydocker

PostgreSQL container logs not displayed

Open
#170 11 comments 0 reactions 0 assignees View on GitHub
bug docker-image
Dominant language
Go
Stars
52.8k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

**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
```bash
> 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](https://user-images.githubusercontent.com/5635462/64673233-e29d6380-d46d-11e9-8171-4415cb5a3bfe.png)

**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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.