New docs: Working with Docker, Custom Deploy Workflows, Cost Management guide

Fresh Produce
1

We’ve published three new guides. If you’re building your own Dockerfiles, hacking on deploy flows, or just trying to make sense of your bill, these might help:

  • Working with Docker on Fly.io
    Get practical advice on working with Docker on Fly.io. Troubleshoot slow builds, optimize image size, prebuild locally, and manage tags more predictably.

  • Custom deploy workflows
    Take control of your deployment flow, whether you’re trying to avoid restarting machines, roll out changes gradually, or update specific parts of your app without touching others.

  • Cost management
    Learn how billing works on Fly.io so you can avoid surprises. Covers VMs, storage, bandwidth, usage estimation, and what tends to sneak up on people.

2 Likes
2

Your app runs as PID 1

Is that true? I though flyd/pilot is always PID 1.

This is why I use an ugly `unshare` workaround for images running with the s6 init system (which is desperate for being PID 1).

1 Like
3

As a small side note, you can now use the new multi-container support instead, whenever PID 1 really is required:

https://community.fly.io/t/fly-io-init-docs-part-2/26411/3

It’s more conceptually elegant, :elegant_crane:, but syntactically it admittedly is 1–3 extra steps still.

Otherwise, you’re right, it’s Fly.io’s own init process visible in that position…

1 Like