Deploy & use Docker Engine running on Fly.io #416
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this, GitHub Actions was using a Docker Engine running on a bare metal host. We were connecting to it via Tailscale. This was OK as a stop-gap, but we ran into issues with:
TAILSCALE_AUTHKEYmax 90d TTL - Generate auth key +Reusable +Ephemeraldagger-buildkitddefault container getting upgraded by a newer dagger CLI (I was using the same Docker Engine)changelog_test_postgrescontainer failing to TCP port (another PostgreSQL was already running)This introduces a dedicated Docker Engine running on Fly.io. It has a cache that persists between runs & is faster than the default GitHub Actions free runner (4 CPUs vs 2 CPUs). The PR includes:
I am looking forward to use Fly machines and spin up this Docker Engine... on the fly 🛫
https://fly.io/docs/reference/machines/
Thanks @mrkurt for https://github.com/fly-apps/docker-daemon - it really helped to get started with this!
For the full story, tune into 🎧 shipit.show/60