So, since the host is mac os, you need to run a linux VM to be able to quickly instantiate a mac os VM?
With Apple's RAM prices?
Looks like your "&&"s might have gotten deleted in the following?
mkdir -p storage docker run -it --rm \ --name lumier-vm \ -p 8006:8006 \ -v $(pwd)/storage:/storage \ -e VM_NAME=lumier-vm \ -e HOST_STORAGE_PATH=$(pwd)/storage \ trycua/lumier:latest
FWIF i prefer the name Laminar
Think Laminar flow, because this is like super smooth macOS VM running in macOS
I'll ask again, since I didn't receive an answer up till now: is it capable of running macOS Big Sur on an ( Apple Silicon{M1 or later} + macOS Monterey{or higher} ) host? If so, would I be able to install apps via App Store on this Big Sur?
Super nice! Do you think it's possible to run XCode and do an app build with this approach?
Would it be possible to spin up VMs inside of a https://aws.amazon.com/ec2/instance-types/mac/?
I already do this with UTM. Whats the difference? Worth converting?
Would Lumier allow me to virtualize macOS with system integrity protection (SIP) disabled?
how does the docker guest orchestrate a completely different virtualization system? is the guest container in docker given access to the host system to then spin up the apple vm guest? to me this seems very risky in terms of security.
Slightly off topic, does anyone know a good way to run Mac VMs on Linux hosts?
This is not "running macOS VMs in Docker".
This is "running debian noVNC clients in Docker that connect to the same macOS host system".
I mean it's great that you use the Apple Virtualization Framework for that on the host service, but that's a different type of VM than a docker VM which would assume syscalls to be abstracted inside the docker container and not on a host service.
But yeah, just my two cents, I guess.
[flagged]
[flagged]
From what I understand VM does _not_ run in docker. The management interface does and connects to the VM running on macOS ARM host via Apple Virtualization Framework.