A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Follow the instructions. Confirm docker compose up works locally
Note when deploying to fly, there is an warning: WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
Try to visit url, doesn't work.
Check fly.io dashboard, app is suspended.
fly deploy and fly scale do not unsuspend
Edit: I was eventually able to resolve by repeated trying to restart machines
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
OS: [e.g. macOS, Windows]
Browser (if applies) [e.g. chrome, safari]
details
First, an error on fly launch --copy-config
$ fly launch --copy-config
...
✓ Configuration is valid
==> Building image
WARN Failed to start remote builder heartbeat: failed to restart VM e82403da761078: failed_precondition: unable to restart machine, not currently started or stopped
==> Building image
WARN Failed to start remote builder heartbeat: failed to restart VM e82403da761078: failed_precondition: unable to restart machine, not currently started or stopped
Error: failed to fetch an image or build from source: failed to restart VM e82403da761078: failed_precondition: unable to restart machine, not currently started or stopped (Request ID: 01J2FMANDN7KK5HR601QRJGTT8-lga) (Trace ID: 1df427b81bf44769036e52bf0c65a865)
After fly secrets import < .env, fly deploy seems to work, but gives a warning:
--> Pushing image done
image: registry.fly.io/supabase-grafana-metrics-sparkling-sunset-9888:deployment-01J2FKS2ZQ94DK91D63Z2GKQCJ
image size: 681 MB
Watch your deployment at https://fly.io/apps/supabase-grafana-metrics-sparkling-sunset-9888/monitoring
Provisioning ips for supabase-grafana-metrics-sparkling-sunset-9888
Dedicated ipv6: 2a09:8280:1::3c:44c6:0
Shared ipv4: 66.241.125.216
Add a dedicated ipv4 with: fly ips allocate-v4
Creating a 1 GB volume named 'supabase_metrics_data' for process group 'app'. Use 'fly vol extend' to increase its size
This deployment will:
* create 1 "app" machine
No machines in group app, launching a new machine
WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
You can fix this by configuring your app to listen on the following addresses:
- 0.0.0.0:8080
Found these processes inside the machine with open listening sockets:
PROCESS | ADDRESSES
-----------------*--------------------------------------
/.fly/hallpass | [fdaa:9:8751:a7b:cb:8fbe:b453:2]:22
Finished launching new machines
-------
✔ Machine 080eee5a591038 [app] update finished: success
-------
Checking DNS configuration for supabase-grafana-metrics-sparkling-sunset-9888.fly.dev
Visit your newly deployed app at https://supabase-grafana-metrics-sparkling-sunset-9888.fly.dev/
Bug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
docker compose up
works locallyWARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
fly deploy
andfly scale
do not unsuspendEdit: I was eventually able to resolve by repeated trying to restart machines
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
details
First, an error on
fly launch --copy-config
After
fly secrets import < .env
,fly deploy
seems to work, but gives a warning: