apt: command not found on ZimaOS does not mean sudo is broken. It means ZimaOS is not Ubuntu or Debian and does not include the APT package-management workflow those distributions use. The October 2024 source user was logged in as root and through ttydBridge but still could not update or install host packages because that is not how ZimaOS is designed.
Current IceWhale documentation now makes the architecture clearer: ZimaOS is Buildroot-based, most system folders are read-only even as root, and applications are expected to run through containers rather than being installed into the host operating system with apt, yum, or similar tools.
sudo Was Not the Problem
The original user thought “sudo commands” were failing because commands such as sudo apt ... returned command-not-found errors.
sudo only changes the privilege context. It cannot create a package manager that is not installed in the operating system.
ZimaOS Is Buildroot-Based
Current IceWhale guides describe ZimaOS as an appliance-style Buildroot system. Buildroot produces a compact embedded Linux image rather than a general-purpose distribution with a mutable package database and normal APT repositories.
This is why trying Debian/Ubuntu package-management tutorials on the ZimaOS host often fails even though many familiar Linux commands are present.
Most System Directories Are Intentionally Read-Only
Current ZimaOS CLI guidance says most system folders remain read-only even when the user logs in as root. Writable user and application data belongs under /DATA.
Use the current ZimaOS CLI filesystem model before trying to modify the base operating system.
Use Docker for Server Applications
If a tutorial says “install this daemon with apt,” first check whether the same application has a maintained Docker image or Compose stack. That is the native ZimaOS application model and keeps dependencies separate from the immutable host.
This applies to media servers, monitoring tools, databases, VPN clients, automation platforms, document services, and many other homelab applications.
Use ZVM When the Software Really Needs a Full Debian/Ubuntu Host
Some applications expect systemd, a package manager, kernel modules, or several OS-level services. In that case, a Debian or Ubuntu VM is a better fit than trying to force the ZimaOS host into behaving like one.
Inside the VM, normal apt package management works because the guest operating system is actually Debian/Ubuntu.
SSH and ttydBridge Still Have a Purpose
The fact that package installation is unsupported does not make the command line useless. SSH and the web terminal remain valuable for inspection, logs, Docker commands, file operations under writable storage, and advanced troubleshooting.
Current IceWhale guidance supports both SSH and a browser terminal through Developer Mode.
The Source User's Jellyfin Problem Was Unrelated to apt
The original poster later mentioned that some videos played in Files but not in Jellyfin. IceWhale/community replies redirected them toward Docker media-path configuration.
That is the correct separation: a playback or library issue inside Jellyfin should be debugged through the app's volume mappings, codecs, transcoding, and logs—not by installing random host packages with APT.
ZimaOS apt FAQ
Can I install apt on the ZimaOS host?
ZimaOS is not designed around APT package management; use containers or a VM instead of treating the host as Debian.
Does root access make system folders writable?
No. Current ZimaOS intentionally keeps most system folders read-only even for root.
Where should custom scripts and writable files live?
Use a writable location under /DATA or another managed data storage path.
