When I was working on my first fly app, I got a lot of help from the good folks at fly getting my dockerfile and github action wired up. Now I’m trying to understand why using docker/setup-buildx-action, actions/cache, docker/login-action, and docker/build-push-action to finally just run fly deploy …

Remote builds are probably fine from GitHub these days. They’re more intricate though. flyctl connects to remote builders over WireGuard. GitHub actions need to create a new WireGuard peer in our stack for every run, wait for it to be provisioned, then start their build. This is reasonably fast and…

Why bother with Docker buildx?

ignoramous January 29, 2023, 8:25am 5

Technically, flyctl deploy --local-only is enough for most cases; but some folks might want to push out prebuilt docker images to Fly (ex1, ex2, ex3).

Topic		Replies	Views
Github Action for Deployment - Dockerfile not found	2	267	July 23, 2023
Dockerfile not found Questions / Help	4	676	July 23, 2023
Problems with Github Actions for CD Path Questions / Help	4	651	September 27, 2023
Innacurate Guide Questions / Help	3	1341	January 13, 2023
Images built with the latest docker buildx and or github actions work again announcement	3	2721	March 24, 2023

Why bother with Docker buildx?

Related topics