Repository navigation
ZimaOS VMÂ #2240
Description
Activity
The ZimaOS VM script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/vm/zimaos-vm.sh)"Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1543889126766420019
Tested
vm/zimaos-vm.shon PVE 9 (Q35, UEFI, 4 cores / 4 GB / 64 GB, local storage). It aborts beforeqm create, so none of the actual test items above can be reached yet:⠸ Retrieving the URL for the ZimaOS installer [ERROR] in line 101: exit code 1: while executing command ZIMAOS_VERSION="$(echo "$FILENAME" | grep -oP 'zimaos-x86_64-\K[0-9.]+(?=_installer)')"This is the "GitHub API version lookup" item, though not the rate-limit half of it — the URL resolves fine, it is the version parse that fails.
Cause. Line 101 only accepts digits and dots for the version. IceWhale tags pre-releases without setting the GitHub prerelease flag, so
releases/latestis currently a beta:$ curl -s https://api.github.com/repos/IceWhaleTech/ZimaOS/releases/latest | jq '{tag_name, prerelease}' { "tag_name": "1.8.0-beta1", "prerelease": false }The filename is therefore
zimaos-x86_64-1.8.0-beta1_installer.iso,[0-9.]+matches nothing before_installer, grep exits 1, andset -eends the run. Nothing host-specific — anyone running the one-liner hits it as long as a beta sits atreleases/latest.Workaround for other testers in the meantime, pinning the last stable release:
curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/vm/zimaos-vm.sh -o /tmp/zimaos-vm.sh sed -i 's|releases/latest|releases/tags/1.7.1|' /tmp/zimaos-vm.sh bash /tmp/zimaos-vm.sh(Download to a file rather than piping into
bash, so the whiptail menus keep a TTY on stdin.)Fix: #2312 takes the version from the release JSON's
tag_nameinstead of parsing the filename, and makes a parse miss non-fatal.One thing worth a maintainer decision, separate from the crash: since upstream does not flag its betas,
releases/latestmeans the script installs 1.8.0-beta1 rather than stable 1.7.1. If a NAS OS should default to stable, the release selection needs its own change (skip-(beta|rc|alpha)tags, or pin). I left that out of #2312 as a policy call and can follow up if you want it.I will pick the remaining test items back up once this is unblocked.
A PR has been created for zimaos-vm: community-scripts/ProxmoxVE#17778
Merged with #17778 in ProxmoxVE
Files deleted with PR #2394
Name of the Script
ZimaOS-VM
Script Type
VM (Virtual Machine)
Does this script support arm64?
arm64 not supported
📋 Script Details
vm/zimaos-vm.sh— creates a ZimaOS VM. ZimaOS is the successor to CasaOS: NAS operating system with an app store, ZFS-backed storage and A/B system updates (https://github.com/IceWhaleTech/ZimaOS).The upstream Proxmox guide is out of date and this script deliberately does not follow it. zimaos-rauc#5, which the ZimaOS README links to, imports a ready-made
.imgas the system disk. That image stopped being published around 1.0 — release 1.7.1 ships only_installer.iso,_installer.imgand a.raucbupdate bundle. So this follows the ISO path thatcachyos-vmandtruenas-vmalready use: boot the installer, let it write the disk.Carried over from that guide:
virtio-scsi-singleand UEFI. Its step 5 — disabling Secure Boot by hand in the OVMF device manager — is unnecessary here because core already setspre-enrolled-keys=0.Defaults: 4 cores, 4 GB RAM, 64 GB disk. ISO is cached under
/var/lib/vz/template/isowith a size guard, since a redirect to an error page still returns 200.What to test
scsi0and the VM boots from disk after the ISO is detachedpre-enrolled-keys=0, or the manual OVMF step is still needed