Host github act runner on docker

[Flash303]

Is it possible to run github act runner in a docker container?
I've already tried, but I get this error:
running as root
success
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

[ChristopherHX]

If you not use the systemd for installation in docker, this should work

e.g. use

• github-act-runner configure ... to configure
• github-act-runner run as final command

[Flash303]

I managed to launch it under container, but act doesn't launch a new container, is this normal?

[ChristopherHX]

I preconfigured act to not launch another container follows actions/runner default if you do not explicitly want it

e.g. add to job
container: mydockerimage:latest

This is more flexible than doing it on the runner

[Flash303]

Yes, i have already try it, but i have this error :
failed to create container: 'Error response from daemon: invalid mount config for type "volume": invalid specification: destination can't be '/''

I think act try to create a volume beetwen the runner and the worker.

There is a way to fix this ?

[ChristopherHX]

Change your working directory away from / in your Dockerfile

[ChristopherHX]

act itself has the same bug

[Flash303]

Thanks it work

[Flash303]

Hello, today I have a new problem with it. Could you help me?
Error :
Error: ❌ Failure - Main 🔄 Checkout
Error: failed to copy content to container: error during connect: Put "http://%2Fvar%2Frun%2Fdocker.sock/v1.49/containers/53d8c2717a104a8a89ea5b612e088624decb5fbbda70502027b536f6e7f2cace/archive?noOverwriteDirNonDir=***&path=%2Fvar%2Frun%2Fact%2Factions%2Factions-checkout%40v3%2F": io: read/write on closed pipe

[ChristopherHX]

Is this a permanent error that appears on every run? Is this a regression of release v0.11.0, I am technically able to backport GitHub Compatibility to v0.10.0 that has a much older / different implementation.

How to reproduce it, is actions/checkout@v3 enough. It is possible to add auto retries if this does not affect every run.

[Flash303]

Yes, every time I run this action I get that error.

On another, completely different action, I get a different error.
To reproduce it, I guess just running any action with a checkout should be enough.

For your information, my act runs inside a Docker container, and it correctly creates one container per action, etc.
I don’t think my configuration is the issue, right?

Error of the different action :
⭐ Run Main actions/checkout@v3
❓ add-matcher /root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/problem-matcher.json
Syncing repository: ElyrionMC/ElySpigot
Getting Git version info
⚙ ***
Temporarily overriding HOME='/root/.cache/act/71bc9d6b797a5db0/tmp/e5937b33-7e39-453a-880f-53f8659ce780' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
/usr/bin/git config --global --add safe.directory /root/.cache/act/71bc9d6b797a5db0/hostexecutor
Deleting the contents of '/root/.cache/act/71bc9d6b797a5db0/hostexecutor'
Initializing the repository
Disabling automatic garbage collection
Setting up auth
Fetching the repository
Determining the checkout info
Checking out the ref
/usr/bin/git log -1 --format='%H'
'956efd9a6a8656638e652b2f484c78968eb6b3a7'
❓ ::remove-matcher owner=checkout-git::
(node:1957) UnhandledPromiseRejectionWarning: Error: File was unable to be removed TypeError: ioUtil.rm is not a function
at Object. (/root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:6054:19)
at Generator.next ()
at /root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:5950:71
at new Promise ()
at webpack_modules.7436.__awaiter (/root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:5946:12)
at Object.rmRF (/root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:6036:12)
at GitAuthHelper. (/root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:291:26)
at Generator.next ()
at /root/.cache/act/71bc9d6b797a5db0/act/actions/actions-checkout@v3/dist/index.js:130:71
at new Promise ()
(node:1957) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:1957) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✅ Success - Main actions/checkout@v3
1s
⭐ Run Main Set up JDK 8
/root/.cache/act/71bc9d6b797a5db0/act/actions/actions-setup-java@v4/dist/setup/index.js:92649
const responseObject = new Response(response.body?.source ?? null)
^

SyntaxError: Unexpected token '.'
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
at internal/main/run_main_module.js:17:47
Error: ❌ Failure - Main Set up JDK 8
Error: exit status 1