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).
I'm excited to play with lume! My use case is adding native Mac execution to Dagger (https://dagger.io) :)
The relevant code is here: https://github.com/trycua/cua/blob/main/libs/lume/src/Contai...
And thanks again - really appreciate the interest. I’ll follow up via email, would love to hear more about the Dagger use case and how native Mac execution fits in!
