fix: use podman --remote for builds via host socket

Building images inside an unprivileged container fails on remount.
Use podman --remote with the runner-mounted podman socket to
delegate builds to the host engine.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.gitea/workflows/ci.yaml

@@ -32,17 +32,17 @@ jobs:
     needs: [test, secrets]
     runs-on: linux
     container: quay.io/podman/stable
+    env:
+      CONTAINER_HOST: unix:///var/run/docker.sock
     steps:
-      - run: |
-          dnf install -y git
-          printf '[storage]\ndriver = "vfs"\n' > /etc/containers/storage.conf
+      - run: dnf install -y git
       - run: |
           git clone --depth 1 \
             -c "http.extraHeader=Authorization: token ${{ github.token }}" \
             "${{ github.server_url }}/${{ github.repository }}.git" .
-      - run: echo "$HARBOR_PASS" | podman login -u "$HARBOR_USER" --password-stdin harbor.mymx.me
+      - run: echo "$HARBOR_PASS" | podman --remote login -u "$HARBOR_USER" --password-stdin harbor.mymx.me
         env:
           HARBOR_USER: ${{ secrets.HARBOR_USER }}
           HARBOR_PASS: ${{ secrets.HARBOR_PASS }}
-      - run: podman build -t harbor.mymx.me/s5p/s5p:latest -f Containerfile .
-      - run: podman push harbor.mymx.me/s5p/s5p:latest
+      - run: podman --remote build -t harbor.mymx.me/s5p/s5p:latest -f Containerfile .
+      - run: podman --remote push harbor.mymx.me/s5p/s5p:latest