orka vm push.
Restart after NVRAM changes
Settings stored in the VM’s NVRAM, such asboot-args or other variables you set with sudo nvram, reach the VM’s files on the node only when macOS restarts. If you push right after changing them, VMs deployed from the image come up without the change.
Restart from inside the guest, then confirm the value survived before you push:
Let work inside the VM finish
Orka copies the VM’s disk while the VM keeps running. Let installs, builds, and downloads finish, and quit apps that are writing to disk, so the image doesn’t capture a half-written state.Remove secrets
Every VM deployed from the image gets a copy of everything on its disk. Before you push, remove anything you used during setup that shouldn’t be in every VM:-
Git credentials,
.netrcfiles, SSH private keys, registry logins, and CI agent tokens. -
Tokens embedded in the remote URLs of repositories you cloned into the image. Check with
git remote -v. -
The User Data log, if the VM ran a User Data script that printed anything sensitive. Its output is in
/var/log/orka/userdata.logand travels with the image. See Bootstrap VMs with User Data. -
Shell history, which can hold secrets you typed. Clear it as the last step:
admin password before you push, so VMs from the image don’t inherit it. See Understanding Orka credentials.

