CI: Docker build/push actions incompatible with Forgejo runner #4

Closed
opened 2026-05-14 05:34:41 +00:00 by Mark · 1 comment
Owner

CI: Docker build/push actions incompatible with Forgejo runner

Symptom

The ci.yml workflow uses docker/setup-buildx-action@v3, docker/build-push-action@v5, and docker/metadata-action@v5 which have compatibility issues with Forgejo's act_runner. The build step fails because Docker-in-Docker is not properly set up.

Context

  • The runner connects to Podman via docker_host: "tcp://127.0.0.1:12345" (proxy)
  • Third-party Docker actions expect direct Docker socket access
  • The runner's base container has no Docker daemon inside it

Suggested fix

Replace GitHub Docker actions with native docker build / docker push CLI commands in the workflow. For example:

- name: Build and push
  run: |
    docker build -t myapp:${{ github.sha }} .
    # Add docker push if registry configured

This repo already uses https://git.forgejo.org/actions/checkout@v4 (Forgejo-native) for checkout, which is good practice.

## CI: Docker build/push actions incompatible with Forgejo runner ### Symptom The `ci.yml` workflow uses `docker/setup-buildx-action@v3`, `docker/build-push-action@v5`, and `docker/metadata-action@v5` which have compatibility issues with Forgejo's act_runner. The build step fails because Docker-in-Docker is not properly set up. ### Context - The runner connects to Podman via `docker_host: "tcp://127.0.0.1:12345"` (proxy) - Third-party Docker actions expect direct Docker socket access - The runner's base container has no Docker daemon inside it ### Suggested fix Replace GitHub Docker actions with native `docker build` / `docker push` CLI commands in the workflow. For example: ```yaml - name: Build and push run: | docker build -t myapp:${{ github.sha }} . # Add docker push if registry configured ``` This repo already uses `https://git.forgejo.org/actions/checkout@v4` (Forgejo-native) for checkout, which is good practice.
Author
Owner

Fixed in commit. Closing.

Fixed in commit. Closing.
Mark closed this issue 2026-05-14 10:37:18 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/GSD2_PM#4
No description provided.