Sorry to necro an old thread, but I tried re-deploying SB this morning to on fly.io to get all the v2 hotness and my machine in fly.io won’t start. I think it’s because the Dockerfile is using tini and fly.io doesn’t like that very much, but I’m not sure. It didn’t used to have this problem, so I’m a little stumped. Maybe the tini thing is a red herring and it’s something else. I was wondering if anyone else has seen this and fixed it; I don’t have time to go spelunking right now but I will later on tonight.
Here are the logs I think are relevant:
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info] INFO Preparing to run: `/sbin/tini -- /docker-entrypoint.sh` as root
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info] INFO [fly api proxy] listening at /.fly/api
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info][WARN tini (655)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]Will run SilverBullet with UID 0, inferred from the owner of /space (set PUID environment variable to override)
2025-09-30T16:11:52Z runner[d899455a6e1198] dfw [info]Machine created and started in 7.129s
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]2025/09/30 16:11:52 User authentication enabled for user "drhayes" with lockout limit 10 and lockout time 60s
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]2025/09/30 16:11:52 Local shell command execution enabled for ALL commands.
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]2025/09/30 16:11:52 SilverBullet is now running: http://:::3000
2025-09-30T16:11:52Z app[d899455a6e1198] dfw [info]2025/09/30 16:11:52 INFO SSH listening listen_address=[fdaa:0:45cf:a7b:41e:9670:3225:2]:22
2025-09-30T16:11:53Z app[d899455a6e1198] dfw [info] INFO Main child exited normally with code: 0
Fly deployments own PID 1 and don’t like having other things running as init (like tini): Multiple processes inside a Fly.io app · Fly Docs