docker image issue

[ravarage]

I Follow docker installation docker run -it -p 8080:8080 clidey/whodb I did also tried with latest tag my docker ps log 68fac9b18d06 clidey/whodb "/core" About a minute ago Exited (2) 13 seconds ago cranky_shockley 72db39c4cdcc clidey/whodb:latest "/core" 24 hours ago Exited (2) 24 hours ago vigorous_galois

I am running ubuntu 22.04

[hkdeman]

Thank you for pointing this out!

Do you see any memory constraints in your docker installation? (it is very light so it is unlikely)

Could you also share the docker version? I can try reproducing this - if you can also upgrade the docker version and try again - that would be awesome!

[11notes]

@ravarage you can use my image if you like: https://hub.docker.com/r/11notes/whodb

[ravarage]

@11notes accodring to log it get reqeust but on browser I get This site can’t be reachedlocalhost refused to connect.

redis     | 1:C 09 Jul 2024 15:28:58.108 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis     | 1:C 09 Jul 2024 15:28:58.108 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis     | 1:C 09 Jul 2024 15:28:58.108 * Redis version=7.2.5, bits=64, commit=00000000, modified=0, pid=1, just started
redis     | 1:C 09 Jul 2024 15:28:58.108 * Configuration loaded
redis     | 1:M 09 Jul 2024 15:28:58.109 * monotonic clock: POSIX clock_gettime
redis     | 1:M 09 Jul 2024 15:28:58.167 * Running mode=standalone, port=6379.
redis     | 1:M 09 Jul 2024 15:28:58.168 * Server initialized
redis     | 1:M 09 Jul 2024 15:28:58.170 * Creating AOF base file appendonly.aof.1.base.rdb on server start
redis     | 1:M 09 Jul 2024 15:28:58.172 * Creating AOF incr file appendonly.aof.1.incr.aof on server start
redis     | 1:M 09 Jul 2024 15:28:58.172 * Ready to accept connections tcp
postgres  | {"time":"2024-07-09T13:29:00.000Z","type":"INF","msg":"starting postgres"}
postgres  | 2024-07-09 13:29:00.502 GMT [1] LOG:  redirecting log output to logging collector process
postgres  | 2024-07-09 13:29:00.502 GMT [1] HINT:  Future log output will appear in directory "/postgres/log".
postgres  | {"timestamp":"2024-07-09 13:29:00.502 GMT","pid":1,"session_id":"668d3b1c.1","line_num":1,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"ending log output to stderr","hint":"Future log output will go to log destination \"jsonlog\".","backend_type":"postmaster","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.502 GMT","pid":1,"session_id":"668d3b1c.1","line_num":2,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"starting PostgreSQL 16.2 on x86_64-alpine-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit","backend_type":"postmaster","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.502 GMT","pid":1,"session_id":"668d3b1c.1","line_num":3,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"listening on IPv4 address \"0.0.0.0\", port 5432","backend_type":"postmaster","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.502 GMT","pid":1,"session_id":"668d3b1c.1","line_num":4,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"listening on IPv6 address \"::\", port 5432","backend_type":"postmaster","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.506 GMT","pid":1,"session_id":"668d3b1c.1","line_num":5,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"listening on Unix socket \"/run/postgresql/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.568 GMT","pid":29,"session_id":"668d3b1c.1d","line_num":1,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"database system was shut down at 2024-07-09 13:28:58 GMT","backend_type":"startup","query_id":0}
postgres  | {"timestamp":"2024-07-09 13:29:00.577 GMT","pid":1,"session_id":"668d3b1c.1","line_num":6,"session_start":"2024-07-09 13:29:00 GMT","txid":0,"error_severity":"LOG","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":0}
whodb     | 2024/07/09 15:29:27 [0e1c38947c18/GjAaiJbFTp-000001] "HEAD http://localhost:8080/ HTTP/1.1" from [::1]:59352 - 200 662B in 29.264µs
whodb     | 2024/07/09 15:29:57 [0e1c38947c18/GjAaiJbFTp-000002] "HEAD http://localhost:8080/ HTTP/1.1" from [::1]:46432 - 200 662B in 29.122µs

[11notes]

whodb | 2024/07/09 15:29:27 [0e1c38947c18/GjAaiJbFTp-000001] "HEAD http://localhost:8080/ HTTP/1.1" from [::1]:59352 - 200 662B in 29.264µs

you get HTTP 200 so all is okay.

[hkdeman]

@ravarage just to confirm, are you still facing this issue? I haven't been able to reproduce this bug unfortunately

[hkdeman]

@ravarage closing this issue due to inactivity but you are welcome to open it if you still face this issue!