ZimaOS Is Not a General-Purpose Package-Managed Linux Distribution
A user connected to a fresh ZimaOS 1.5.4 installation over SSH and found that curl and jq worked while apt-get, opkg, apk, openssl, and docker-compose were unavailable.
The reply explained that package managers from other Linux distributions cannot be used on ZimaOS. Their absence was an operating-system design boundary, not evidence that SSH itself was incomplete.
Use docker compose Instead of docker-compose
The older standalone Compose command uses a hyphen:
docker-composeThe reply recommended testing the current Docker CLI plugin syntax instead:
docker composeScripts copied from older Linux guides may therefore fail even when Compose functionality is available through Docker.
Deploy Additional Services as Containers
The user wanted the missing commands in order to install NetBird on the host. The community answer recommended deploying NetBird through Docker rather than trying to turn the ZimaOS base system into Debian, Alpine, or OpenWrt with a foreign package manager.
This keeps the service and its dependencies inside a containerized environment. It also avoids depending on host changes that may be unavailable or replaced by later system updates.
Do Not Assume Every Familiar Utility Is Installed
SSH provides a shell into the system; it does not guarantee that every common Linux executable is present. Before following a third-party installation script, inspect its dependencies and determine whether it expects a mutable host, system packages, or system services that ZimaOS does not expose.
Version Boundary
This two-reply discussion concerns ZimaOS 1.5.4 in March 2026. It establishes the package-manager boundary and Compose command suggested at that time, but it does not document whether later releases added specific utilities.
FAQ
Can apt-get be enabled from SSH on ZimaOS?
The reply says package managers such as apt-get, opkg, and apk are not supported as they would be on their native distributions.
Is Docker Compose completely missing?
Not necessarily. The recommended command was docker compose rather than the older docker-compose executable.
