Execute Lifecycle Event Scripts on Host Machine

[KevinHaendel]

Is your feature request related to a problem?

Yes: Currently we cannot have nested virualization if the Guest OS is MacOS.
That means we can't have MacOS Guests running Docker. A workaround would be to run docker remotely - e.g. isolated in the Host Machine.

What solution would you like?

Implementing docker support would be part of another feature request, therefor the simplest solution is to implement Script hooks running on the host machine to manage a clean docker environment for each GitHub Actions run ourselves.
Those scripts running on the host machine could be used for any other usecase aswell.

What alternatives have you considered?

Building the same functionality tartelet provides ourselves.

Any additional context?

No response

[fkorotkov]

@KevinHaendel how are you planning to pass Docker back into the VM? Are you planning just to run services yourself or passing a socket inside the VM?

[KevinHaendel]

@fkorotkov The plan is to run the Docker daemon on the host (or a separate Linux VM that supports nested virtualization) and expose it via a TCP socket or SSH.

Inside the macOS guest, we would configure the Docker CLI to connect to that remote daemon (by setting DOCKER_HOST). This way, the macOS guest can orchestrate containers without needing to run the Docker engine itself, bypassing the nested virtualization limitation.

[fkorotkov]

Yes, sound like a plan and exactly what we are cooking for Cirrus Runners to support Docker. Seems the only option to workaround it.