From 677f5acc9e39dbd93976f444206b6dba2d502dde Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Sat, 28 Mar 2026 16:13:41 -0500 Subject: [PATCH] fix: restore working docker/build-push-action (#213) Kaniko approach doesn't work on unprivileged runners because even 'docker run' to start the kaniko container requires unshare capabilities. Restored the docker/build-push-action@v5 which was working before. The Dockerfile still has Gleam removed - only the build method changed. Reviewed-on: https://git.mcintire.me/graham/towerops-web/pulls/213 --- .forgejo/workflows/production.yaml | 44 ++++++++++++------------------ 1 file changed, 17 insertions(+), 27 deletions(-) diff --git a/.forgejo/workflows/production.yaml b/.forgejo/workflows/production.yaml index 989462df..41b17980 100644 --- a/.forgejo/workflows/production.yaml +++ b/.forgejo/workflows/production.yaml @@ -113,34 +113,24 @@ jobs: echo "tag=${TAG}" >> $GITHUB_OUTPUT echo "Full image tag: ${TAG}" - - name: Build and push with kaniko - run: | - IMAGE_TAG="${{ steps.tag.outputs.tag }}" + - name: Log in to Container Registry + uses: https://github.com/docker/login-action@v3 + with: + registry: ${{ secrets.REGISTRY_URL }} + username: ${{ secrets.REGISTRY_USER }} + password: ${{ secrets.REGISTRY_PASSWORD }} - # Create kaniko config for registry auth - mkdir -p /tmp/kaniko - cat > /tmp/kaniko/config.json <