From db33495d000bf5cf31670820e104ff4f05026686 Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Sun, 29 Mar 2026 11:12:43 -0500 Subject: [PATCH] fix: use docker driver for buildx on unprivileged runner (#219) The build-push-action was trying to use docker-container driver by default, which requires privileged mount operations. This fails on unprivileged runners with vfs storage driver. Solution: Explicitly configure buildx to use 'docker' driver, which uses the regular Docker daemon that's already running with vfs storage. This avoids the need for privileged container mounts. Resolves: operation not permitted during buildkit mount Reviewed-on: https://git.mcintire.me/graham/towerops-web/pulls/219 --- .forgejo/workflows/production.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.forgejo/workflows/production.yaml b/.forgejo/workflows/production.yaml index ed0904c1..3ff87620 100644 --- a/.forgejo/workflows/production.yaml +++ b/.forgejo/workflows/production.yaml @@ -120,6 +120,12 @@ jobs: username: ${{ secrets.REGISTRY_USER }} password: ${{ secrets.REGISTRY_PASSWORD }} + - name: Set up Docker Buildx + uses: https://github.com/docker/setup-buildx-action@v3 + with: + driver: docker + install: true + - name: Build and push Docker image uses: https://github.com/docker/build-push-action@v5 with: