31–40 of 59 posts
Super nice! Do you think it's possible to run XCode and do an app build with this approach?
Slightly off topic, does anyone know a good way to run Mac VMs on Linux hosts?
Slightly off topic, does anyone know a good way to run Mac VMs on Linux hosts?
Apple's licensing requires the host machine to be OSX. You cannot do what you're asking and be in license compliance.
There’s instead no such limitation when running Linux VMs on a macOS host.
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.
been a while since it's come up but does Darwin support kernel level containerization yet? Apple should recognize the use case or utility and run with it.
Usually they are responsive to these feedbacks, we'll try to mention on a existing GH issue: https://github.com/Developer-Ecosystem-Engineering
Super nice! Do you think it's possible to run XCode and do an app build with this approach?
Yes! That’s actually what https://tuist.dev is doing. They use Lume to spin up ephemeral macOS VMs with Xcode preinstalled, so they can run builds in clean, reproducible environments. It’s great for CI workflows where you want full macOS without managing long-lived hosts
Earlier quoted context omitted.
Yes! That’s actually what https://tuist.dev is doing. They use Lume to spin up ephemeral macOS VMs with Xcode preinstalled, so they can run builds in clean, reproducible environments. It’s great for CI workflows where you want full macOS without managing long-lived hosts
Is it possible to build and host our own Mac base images? Or is there a mandatory dependency to Cua's hosted registry?
Currently, lume supports pushing to GitHub Container Registry (GHCR). However, it’s feasible to extend support to any OCI-compatible registry in the future.
Steps to build and push a custom image:
1. Start by creating a new VM or pulling an existing image. Launch the VM, make your desired modifications, and use it as your golden image.
2. Generate a classic access token on GitHub. Then: export GITHUB_USERNAME= export GITHUB_TOKEN=
3. Push your custom image: lume push "" ":" --registry ghcr.io --organization "" --additional-tags ""
Example: lume push "lume_vm" "macos-sequoia-cua:latest" --registry ghcr.io --organization "trycua" --additional-tags "15.2"
Pull your image later with: lume pull "macos-sequoia-cua:latest" --registry ghcr.io --organization "trycua"
There is no mandatory dependency on the Cua-hosted registry - you are free to maintain your own image registry using GHCR or another OCI-compatible alternative (with some extension work).
Earlier quoted context omitted.
Apple's licensing requires the host machine to be OSX. You cannot do what you're asking and be in license compliance.
Correct. Apple's licensing requires macOS to run on Apple hardware, and limits you to 2 concurrent macOS VMs per host. This is enforced by the Apple Vz framework itself. Some KVM-based solutions bypass these checks, but they aren’t compliant for production use. There’s instead no such limitation when running Linux VMs on a macOS host.
[flagged]
Earlier quoted context omitted.
Is it possible to build and host our own Mac base images? Or is there a mandatory dependency to Cua's hosted registry?
Yes, you can build and host your own Mac base images directly using the lume CLI. See the usage guide at: https://github.com/trycua/cua/tree/main/libs/lume#usage Currently, lume supports pushing to GitHub Container Registry (GHCR). However, it’s feasible to extend support to any OCI-compatible registry in the future. Steps to build and push a custom image: 1. Start by creating a new VM or pulling an existing image. L…
I'm excited to play with lume! My use case is adding native Mac execution to Dagger (https://dagger.io) :)
Earlier quoted context omitted.
Not quite, there's no need to run a Linux VM on macOS just to spin up macOS VMs. Since the host is already macOS, we leverage the Apple Virtualization Framework (Vz) directly via a lightweight background service (lume). The Docker container (Lumier) acts purely as a frontend and delivery mechanism for managing and launching VMs — there's no nested virtualization or Linux VM involved. That said, you're absolutely righ…
Docker uses a Linux VM to run on macOS.