Skip to main content
orka vm resize grows a VM’s disk, but starting from an image that’s already the size you need is faster and avoids its side effects:
  • It restarts the VM twice, once after growing the disk and once after repartitioning it.
  • It needs the space up front. The node must have free space for the disk’s new size, plus some headroom, at the moment you run the resize. Images cached on the node count against that space, so a resize can be refused on a node that looks like it has room.
  • macOS updates can fail afterward. Upgrading macOS inside a VM after resizing it might fail. Images pushed from a resized VM carry the same disk layout, so every VM deployed from them is affected too. See the limitations in Apple silicon Mac servers in Orka.

Start from a larger image

MacStadium publishes 200 GB variants of some base images, for example:
Build your CI image on one of these and push it, so every VM deployed from it already has the disk you need. The orka-images repository lists the available images and tags.

If you have to resize

  • Update macOS first, then resize. If a VM is already resized, deploy a fresh VM from an image that wasn’t resized and update that one instead.
  • Resize once, in the image build, not in each CI job. Push the resized VM to a new image and deploy CI VMs from it.
  • Make room on the node if the resize is refused for space. A resize doesn’t remove cached images to make room, so remove cached images you no longer need with orka imagecache remove (Orka 3.6.3 and later), then try again.