[GH-ISSUE #5996] Support the integrated artifact server and cache server when using the `--network` flag to use a network that is not the default `host` networking #1312

New issue

Open

opened 2026-03-01 21:50:18 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:50:18 +03:00

Owner

Originally created by @mozzieongit on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/nektos/act/issues/5996

Act version

0.2.84

Feature description

When running act with --network default on Docker (or --network podman on podman) the artifact or cache servers are not reachable by the containers, as the servers bind on the "public" IP of the host and not the IP of the container network interface.

The feature request is to support those servers when using non-host networking.

As a workaround for the artifact server I previously hacked together a standalone binary based on the act code (see https://github.com/mozzieongit/act/blob/master/bin/standalone-artifact-server.go) and created a separate container running that binary (see the README).
I think the better approach would be to keep it within the one act binary and host the servers on the correct IP.
However, my Go knowledge is not advanced (or even intermediate or beginner for that matter) enough to make a PR myself.

Originally created by @mozzieongit on GitHub (Jan 22, 2026). Original GitHub issue: https://github.com/nektos/act/issues/5996 ### Act version 0.2.84 ### Feature description When running act with `--network default` on Docker (or `--network podman` on podman) the artifact or cache servers are not reachable by the containers, as the servers bind on the "public" IP of the host and not the IP of the container network interface. The feature request is to support those servers when using non-host networking. As a workaround for the artifact server I previously hacked together a standalone binary based on the act code (see https://github.com/mozzieongit/act/blob/master/bin/standalone-artifact-server.go) and created a separate container running that binary (see the [README](https://github.com/mozzieongit/act/)). I think the better approach would be to keep it within the one `act` binary and host the servers on the correct IP. However, my Go knowledge is not advanced (or even intermediate or beginner for that matter) enough to make a PR myself.