podman compose: DHT down after a few seconds

[secretmango]

• I have checked the existing issues to avoid duplicates
• I have redacted any info hashes and content metadata from any logs or screenshots attached to this issue

Describe the bug

After failing to enable bitmagnet with nix, I am trying to run the docker compose with podman compose.

Both the postgresql container and the bitmagnet container seem to be fine and the status says they are up, but after a few seconds, repeatedly, DHT is shown as "Down".

There arent any console errors related to DHT.

To Reproduce

Run the compose.yml with podman compose. All changes I made were adding a TMDB api key and specifying docker.io as source of the postgres image.

Expected behavior

It should at least output the reason why DHT is down.

Environment Information (Required)

• Bitmagnet version: 0.10.0
• OS and version: NixOS unstable, podman version 5.8.2, podman-compose version 1.5.0

Additional context

I opened the bittorrent port in the firewall, no change.

[postgres]  | 
[postgres]  | PostgreSQL Database directory appears to contain a database; Skipping initialization
[postgres]  | 
[postgres]  | 2026-06-07 17:10:02.090 UTC [1] LOG:  starting PostgreSQL 16.14 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[postgres]  | 2026-06-07 17:10:02.090 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[postgres]  | 2026-06-07 17:10:02.090 UTC [1] LOG:  listening on IPv6 address "::", port 5432
[postgres]  | 2026-06-07 17:10:02.092 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[postgres]  | 2026-06-07 17:10:02.096 UTC [25] LOG:  database system was shut down at 2026-06-07 17:09:49 UTC
[postgres]  | 2026-06-07 17:10:02.102 UTC [1] LOG:  database system is ready to accept connections
[bitmagnet] | INFO      migrator        migrations/migrator.go:68       checking and applying migrations...
[bitmagnet] | INFO      migrator        migrations/logger.go:33 goose: no migrations to run. current version: 19
[bitmagnet] | INFO      worker/worker.go:201    started worker  {"key": "queue_server"}
[bitmagnet] | INFO      worker/worker.go:201    started worker  {"key": "http_server"}
[bitmagnet] | INFO      worker/worker.go:201    started worker  {"key": "dht_crawler"}
[postgres]  | 2026-06-07 17:15:02.160 UTC [23] LOG:  checkpoint starting: time
[postgres]  | 2026-06-07 17:15:02.176 UTC [23] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.003 s, total=0.016 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=0 kB; lsn=0/1B4C3F8, redo lsn=0/1B4C3C0
[bitmagnet] | ERROR     tmdb/requester_logger.go:24     request failed  {"path": "/authentication", "queryParams": null, "status": "502 Bad Gateway", "trace": {"DNSLookup":156853645,"ConnTime":265129349,"TCPConnTime":51448521,"TLSHandshake":56690181,"ServerTime":156748297,"ResponseTime":41686,"TotalTime":421884506,"IsConnReused":false,"IsConnWasIdle":false,"ConnIdleTime":0,"RequestAttempt":1,"RemoteAddr":{"IP":"xxxxxxxxx,"Port":443,"Zone":""}}, "error": "TMDB request failed: 502 Bad Gateway"}
[bitmagnet] | github.com/bitmagnet-io/bitmagnet/internal/tmdb.requesterLogger.Request
[bitmagnet] |   /src/internal/tmdb/requester_logger.go:24
[bitmagnet] | github.com/bitmagnet-io/bitmagnet/internal/tmdb.(*requesterLazy).Request
[bitmagnet] |   /src/internal/tmdb/requester_lazy.go:32
[bitmagnet] | github.com/bitmagnet-io/bitmagnet/internal/tmdb.client.ValidateApiKey
[bitmagnet] |   /src/internal/tmdb/client.go:22
[bitmagnet] | github.com/bitmagnet-io/bitmagnet/internal/tmdb/tmdb_health.New.NewCheck.func2
[bitmagnet] |   /src/internal/tmdb/tmdb_health/check.go:26
[bitmagnet] | github.com/bitmagnet-io/bitmagnet/internal/health.executeCheckFunc.func1
[bitmagnet] |   /src/internal/health/check.go:518

this did not change anything

environment:
    - ...
    - log.level debug

[khimaros]

same issue here (also podman compose).

when initially starting the containers, it showed DHT healthy.

then at some point, the server shut itself down, migrations ran, and on start DHT was unhealthy:

[postgres]  | The files belonging to this database system will be owned by user "postgres".
[postgres]  | This user must also own the server process.
[postgres]  | 
[postgres]  | The database cluster will be initialized with locale "en_US.utf8".
[postgres]  | The default database encoding has accordingly been set to "UTF8".
[postgres]  | The default text search configuration will be set to "english".
[postgres]  | 
[postgres]  | Data page checksums are disabled.
[postgres]  | 
[postgres]  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
[postgres]  | creating subdirectories ... ok
[postgres]  | selecting dynamic shared memory implementation ... posix
[postgres]  | selecting default max_connections ... 100
[postgres]  | selecting default shared_buffers ... 128MB
[postgres]  | selecting default time zone ... UTC
[postgres]  | creating configuration files ... ok
[postgres]  | running bootstrap script ... ok
[postgres]  | sh: locale: not found
[postgres]  | 2026-07-12 22:40:59.285 UTC [32] WARNING:  no usable system locales were found
[postgres]  | performing post-bootstrap initialization ... ok
[postgres]  | syncing data to disk ... ok
[postgres]  | 
[postgres]  | 
[postgres]  | Success. You can now start the database server using:
[postgres]  | 
[postgres]  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
[postgres]  | 
[postgres]  | initdb: warning: enabling "trust" authentication for local connections
[postgres]  | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
[postgres]  | waiting for server to start....2026-07-12 22:41:02.420 UTC [38] LOG:  starting PostgreSQL 16.14 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[postgres]  | 2026-07-12 22:41:02.427 UTC [38] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[postgres]  | 2026-07-12 22:41:02.438 UTC [41] LOG:  database system was shut down at 2026-07-12 22:40:59 UTC
[postgres]  | 2026-07-12 22:41:02.445 UTC [38] LOG:  database system is ready to accept connections
[postgres]  |  done
[postgres]  | server started
[postgres]  | CREATE DATABASE
[postgres]  | 
[postgres]  | 
[postgres]  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
[postgres]  | 
[postgres]  | waiting for server to shut down....2026-07-12 22:41:02.560 UTC [38] LOG:  received fast shutdown request
[postgres]  | 2026-07-12 22:41:02.563 UTC [38] LOG:  aborting any active transactions
[postgres]  | 2026-07-12 22:41:02.566 UTC [38] LOG:  background worker "logical replication launcher" (PID 44) exited with exit code 1
[postgres]  | 2026-07-12 22:41:02.566 UTC [39] LOG:  shutting down
[postgres]  | 2026-07-12 22:41:02.569 UTC [39] LOG:  checkpoint starting: shutdown immediate
[postgres]  | 2026-07-12 22:41:03.474 UTC [39] LOG:  checkpoint complete: wrote 926 buffers (5.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.875 s, total=0.908 s; sync files=301, longest=0.010 s, average=0.003 s; distance=4283 kB, estimate=4283 kB; lsn=0/1925D68, redo lsn=0/1925D68
[postgres]  | 2026-07-12 22:41:03.479 UTC [38] LOG:  database system is shut down
[postgres]  |  done
[postgres]  | server stopped
[postgres]  | 
[postgres]  | PostgreSQL init process complete; ready for start up.
[postgres]  | 
[postgres]  | 2026-07-12 22:41:03.584 UTC [1] LOG:  starting PostgreSQL 16.14 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[postgres]  | 2026-07-12 22:41:03.584 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[postgres]  | 2026-07-12 22:41:03.584 UTC [1] LOG:  listening on IPv6 address "::", port 5432
[postgres]  | 2026-07-12 22:41:03.592 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[postgres]  | 2026-07-12 22:41:03.599 UTC [54] LOG:  database system was shut down at 2026-07-12 22:41:03 UTC
[postgres]  | 2026-07-12 22:41:03.607 UTC [1] LOG:  database system is ready to accept connections
[bitmagnet] | WARN	tmdb/requester_lazy.go:40	you are using the default TMDB api key; TMDB requests will be limited to 1 per second; to remove this warning please configure a personal TMDB api key
[bitmagnet] | INFO	migrator	migrations/migrator.go:68	checking and applying migrations...
[postgres]  | 2026-07-12 22:41:10.099 UTC [61] ERROR:  relation "goose_db_version" does not exist at character 36
[postgres]  | 2026-07-12 22:41:10.099 UTC [61] STATEMENT:  SELECT version_id, is_applied from goose_db_version ORDER BY id DESC
[bitmagnet] | INFO	migrator	migrations/logger.go:33	goose: successfully migrated database to version: 19
[bitmagnet] | INFO	worker/worker.go:201	started worker	{"key": "http_server"}
[bitmagnet] | INFO	worker/worker.go:201	started worker	{"key": "dht_crawler"}
[bitmagnet] | INFO	worker/worker.go:201	started worker	{"key": "queue_server"}

[khimaros]

actually, the restart has nothing to do with it.

if i down/up the podman compose, it initially shows "up" and then after about a minute shows "down"

[khimaros]

i'm not sure why, but https://github.com/nbdy/dhtc seems to work with podman on the same machine.

[khimaros]

this is the list of bootstrap nodes which are used by dhtc: https://github.com/nbdy/dhtc/blob/548288c06c8a4ac1765a6e7fdcb7c09502cbfed0/bootstrap-nodes.txt#L4

[khimaros]

i tried adding the same set of bootstrap nodes to bitmagnet and upped the connect timeout to 30s.

no impact, and all return "ping failed" -- maybe the ping should be disabled?