`fly launch` no longer generates a Dockerfile for Astro 5 sites
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Reproduce the issue with a new Astro 5.16.10 project from npm create astro@latest, then run fly launch and inspect the generated configuration. Compare this with the Dockerfile produced by npx --yes @flydotio/dockerfile@latest; the work is done when launch generates a deployable Dockerfile and fly deploy produces an app listening on 0.0.0.0:8080.
Written by the indexing model from the issue text.
Description
Tried to launch and deploy a brand new Astro project using version 5.16.10, using the minimal, recommended template they provide via npm create astro@latest. It creates a fly.toml, but no Dockerfile.
➜ fly launch
Scanning source code
Could not find a Dockerfile, nor detect a runtime or framework from source code. Continuing with a blank app.
I tried using npx --yes @flydotio/dockerfile@latest to generate one, but the resulting Dockerfile doesn't work without modifications. Running fly deploy using that generated Dockerfile results in an app that can't run, I get this:
WARNING The app is listening on the incorrect 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
It's not a major hurdle to get this working right, but thought I might flag this.
- Operating system
fly version
fly v0.4.3 darwin/arm64 Commit: f58ce93c269bf5211a4dba0454631d94e5123dfc BuildDate: 2026-01-12T23:32:09Z
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 311
- Avg merge
- 12h 50m
- Merged PRs (30d)
- 78
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from superfly/flyctl
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100