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
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=<your_github_username>
export GITHUB_TOKEN=<your_github_token>
3. Push your custom image:
lume push "<VM_NAME_TO_PUSH>" "<IMAGE_NAME>:<TAG>" --registry ghcr.io --organization "<your_org_id>" --additional-tags "<optional_additional_tags>"
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).
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?
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. 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=<your_github_username> export GITHUB_TOKEN=<your_github_token>
3. Push your custom image: lume push "<VM_NAME_TO_PUSH>" "<IMAGE_NAME>:<TAG>" --registry ghcr.io --organization "<your_org_id>" --additional-tags "<optional_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).
2 replies →