apt install, apt-get update, and yum install fail on ZimaOS because ZimaOS is not a Debian-, Ubuntu-, Fedora-, or RHEL-style general-purpose distribution. It is built with Buildroot as an appliance OS and keeps most system folders read-only.
Current ZimaOS does now have package-like mechanisms for specific purposes—most notably zpkg modules, and some developer documentation uses Entware/opkg for specialized tooling. Those do not turn the base OS into a normal mutable Linux distro where arbitrary host packages can be installed and integrated like Debian packages.
The Source User Tried apt, apt-get, and yum
The original 2024 post reported that all three package-manager approaches failed over SSH. A community reply explained that ZimaOS is built with Buildroot and combines Linux, glibc, systemd, Docker, and virtualization components without a Debian-style package database.
That architectural explanation remains accurate.
Current ZimaOS Keeps Most System Paths Read-Only
IceWhale's current CLI guidance explicitly says that most system folders remain read-only even as root. User data and app data belong under /DATA.
See the current ZimaOS CLI filesystem model.
For Applications, Docker Is the Primary Extension Model
If software exists as a maintained Docker image or Compose stack, that is usually the most ZimaOS-native deployment route. Dependencies remain inside the container and do not modify the base operating system.
This is why IceWhale's response to the later WebDAV request explored a Docker-based application rather than telling the user to install davfs2 with APT.
zpkg Is a ZimaOS Module Manager, Not apt
Current ZimaOS uses zpkg for installable system modules such as AI/search extensions and community/official modules. A module is built for the ZimaOS extension mechanism and can include its own service policy.
It is not a generic replacement where arbitrary Debian package names such as davfs2 can be installed.
IceWhale Also Documents opkg for Specialized Developer Environments
Current IceWhale Python/developer guidance shows installing Entware under /opt and then using opkg for developer utilities such as git-http.
This is an advanced supported pattern in that particular guide, not permission to assume every Linux daemon installed from Entware will integrate safely with ZimaOS boot, Files, networking, or storage services.
Use the current Entware/opkg developer workflow only when it matches the intended use case.
The Later WebDAV Request Needed Host-Level Integration
The 2025 user wanted a WebDAV cloud drive mounted at the operating-system level so it would become accessible through the ZimaOS Files experience and to other apps. They explicitly said a separate AList-style app was not equivalent.
That requirement is harder than “run a WebDAV client container” because a container mount does not automatically become a native host mount visible to Files and every other container.
A Container Can Still Solve Some WebDAV Workflows
If the real goal is to browse, sync, or copy data to a WebDAV provider, a containerized tool can be safer than altering the host. Examples include sync clients, file managers, or backup tools that support WebDAV directly.
Map only the ZimaOS folders the container needs and keep provider credentials in protected app configuration.
Use a VM When the Software Requires a Normal Mutable Linux Host
If a workflow truly needs apt install davfs2, system packages, FUSE/kernel behavior, or custom boot services, a Debian/Ubuntu VM can be a cleaner boundary. Inside the guest, normal package management is supported because the guest actually is Debian/Ubuntu.
Then expose the mounted data back to ZimaOS or other clients through a deliberate network/storage protocol if needed.
Host Modifications Must Survive the Immutable Lifecycle
Even when an advanced workaround makes a binary available under /opt or /DATA, verify:
- the service starts after reboot;
- it survives OTA updates;
- credentials persist securely;
- the mount exists before dependent apps start;
- failure does not leave apps writing into an empty local mountpoint.
A Host Mount Is Not Automatically a Files Integration
ZimaOS Files is a native service with its own storage and network-location model. Creating a custom FUSE/WebDAV mount from a shell does not guarantee it appears as a first-class Files location or receives the same permissions and lifecycle management.
ZimaOS Package Manager FAQ
Why does apt not work on ZimaOS?
ZimaOS is Buildroot-based and does not use Debian/Ubuntu's APT package-management architecture.
Is zpkg a general replacement for apt?
No. zpkg installs ZimaOS modules built for the platform's module system.
Does IceWhale ever document opkg?
Yes, in a specialized developer/Python setup using Entware under /opt. That does not make the base OS a normal mutable distro.
What if I specifically need davfs2 or another host daemon?
Prefer a supported container/module when available, or run a general-purpose Linux VM when the workflow truly depends on normal package management and host services.
