This action installs Docker on a macOS runner through Colima, Lima-VM, and Homebrew.
I intend this action to be kept as simple as possible:
- No other OS will be supported.
- Binaries will be downloaded directly from the source when possible.
macos-12macos-13
Yes, exactly what you just read. These processors do not support nested virtualization. This means Colima can't start the VM to run Docker.
For the M1 processor there is no hope. It lacks the hardware support for this.
The M2 and M3 processors have such hardware support, but no software support from Apple's Hypervisor framework (so no hopes for QEMU) or Virtualization framework (alternative to QEMU).
I'm sorry, but there's nothing I can do about it. All we can do is wait. If I miss the announcement of nested virtualization support, please open an issue.
- Safety check to ensure the action is running in macOS.
- As simple and lightweight (downloads binaries directly when possible).
The action, by default, will not try to upgrade QEMU if it's already installed. The reason is that installing QEMU takes a considerable amount of time.
If this is set to "true", the action will attempt an upgrade of QEMU to the
latest version available in Homebrew.
The version of Lima to install. This can be any valid version from Lima releases page
The version of Colima to install. This can be any valid version from Colima releases page
Starts Colima with a reachable network address through passing --network-address
to the colima start command. Startup will be slower.
The version of Colima that was installed.
The version of the Docker client that was installed.
The version of Docker Compose that was installed.