Error cleaning up network in self-hosted mode #255

New Issue

Matt0009 · 2023-06-26T08:53:53Z

Matt0009 commented

2023-06-26 08:53:53 +00:00

When running latest stable release in self-hosted on a windows 10 machine

This occurs when cleaning up the network in any workflow I write:

[Build Validation/build] Error while cleaning network: error during connect: this error may indicate that the docker daemon is not running: Delete "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/networks/GITEA-ACTIONS-TASK-17_WORKFLOW-Build-Validation_JOB-build-network": open //./pipe/docker_engine: The system cannot find the file specified.

When running latest stable release in self-hosted on a windows 10 machine This occurs when cleaning up the network in any workflow I write: `[Build Validation/build] Error while cleaning network: error during connect: this error may indicate that the docker daemon is not running: Delete "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/networks/GITEA-ACTIONS-TASK-17_WORKFLOW-Build-Validation_JOB-build-network": open //./pipe/docker_engine: The system cannot find the file specified.`

👍 1

wolfogre commented

2023-06-27 08:31:02 +00:00

Weird. So you're sure act runner has started job containers, but cannot clean networks, right?

Could you please show us the output of

docker network ls

Weird. So you're sure act runner has started job containers, but cannot clean networks, right? Could you please show us the output of ```bash docker network ls ```

wolfogre added the

kind

bug

label 2023-06-27 08:31:12 +00:00

Matt0009 commented

2023-06-27 08:33:47 +00:00

It's just running with the windows.exe with the self-hosted label on, not actually using the docker setup for this

wolfogre commented

2023-06-27 08:53:07 +00:00

I see. One more question, could you show us the version of your act_runner by ./act_runner -v, and the labels config in .runner file?

I see. One more question, could you show us the version of your act_runner by `./act_runner -v`, and the labels config in `.runner` file?

Zettat123 commented

2023-06-27 09:06:54 +00:00

It's a bug caused by

		pkg/runner/run_context.go
		Lines 401 to 405 in 515c2c429d
	
				func (rc *RunContext) removeNetwork(name string) common.Executor {

					return func(ctx context.Context) error {

						return container.NewDockerNetworkRemoveExecutor(name)(ctx)

					}

				}