I have two environments “stage” and “prod”.
When I deploy the very same dockerfile to prod, the app never starts with following errors:
>flyctl deploy --remote-only -c fly.prod.toml --image registry.fly.io/prod-XXX:b368cc5ac4b01705755bc4c4dd327cef36ff907d
...
machine is in a non-startable state: created
Successfully prepared image registry.fly.io/prod-XXX:b368cc5ac4b01705755bc4c4dd327cef36ff907d (14.127193531s)
Setting up volume 'tmp_data'
Opening encrypted volume
Configuring firecracker
machine is in a non-startable state: created
INFO Sending signal SIGINT to main child process w/ PID 313
machine is in a non-startable state: created
machine is in a non-startable state: created
machine is in a non-startable state: created
INFO Main child exited with signal (with signal 'SIGINT', core dumped? false)
INFO Starting clean up.
INFO Umounting /dev/vdb from /tmp
WARN hallpass exited, pid: 314, status: signal: 15 (SIGTERM)
2024/01/18 10:05:36 listening on [fdaa:2:6854:a7b:23c2:75bc:a40d:2]:22 (DNS: [fdaa::3]:53)
[ 1220.703493] reboot: Restarting system
[ 0.035853] PCI: Fatal: No config space access function found
INFO Starting init (commit: 8995e367)...
INFO Mounting /dev/vdb at /tmp w/ uid: 0, gid: 0 and chmod 0755
INFO Resized /tmp to 5364514816 bytes
INFO Preparing to run: `/usr/local/bin/server` as root
INFO [fly api proxy] listening at /.fly/api
2024/01/18 10:05:38 listening on [fdaa:2:6854:a7b:23c2:75bc:a40d:2]:22 (DNS: [fdaa::3]:53)
INFO Main child exited with signal (with signal 'SIGSEGV', core dumped? false)
INFO Starting clean up.
INFO Umounting /dev/vdb from /tmp
WARN hallpass exited, pid: 314, status: signal: 15 (SIGTERM)
2024/01/18 10:05:39 listening on [fdaa:2:6854:a7b:23c2:75bc:a40d:2]:22 (DNS: [fdaa::3]:53)
On stage, everything works fine. Anyone got an idea what the problem could be?