Bottom Line: A Working Pterodactyl Panel Does Not Mean Wings Can Be Installed as Another ZimaOS App
Panel and Wings have different roles. Panel is the web control plane. Wings is the node daemon that talks to Docker, manages game-server containers and expects host-level Linux integration. That is why getting Panel running in Docker does not automatically create a supported place for Wings.
Wings Expects a General-Purpose Linux Host With Docker
The official Wings installation guide lists supported Linux distributions and requires a system capable of running Docker. Pterodactyl also warns that some nested/containerized virtualization environments can prevent Wings from working correctly.
Its Wings configuration documentation assumes direct control over the node daemon, networking and Docker integration.
Why Stock ZimaOS Is an Awkward Direct Wings Host
ZimaOS is an appliance-style Buildroot system. Normal host package instructions written for Debian/Ubuntu do not map cleanly to it. The ZimaOS package-manager guide explains why apt/yum are not the normal extension model.
The Cleaner Architecture: Run Wings in a Supported Linux VM
Use a Debian or Ubuntu VM and give it enough CPU, RAM, SSD space and network access for your game servers. Then install Docker and Wings using the upstream procedure inside that VM. This keeps Pterodactyl's expected host model intact instead of modifying the ZimaOS base system.
The Virtual Machine Manager hardware guide is useful for guest resource planning, and the Zima VM overview shows the current virtualization direction.
Security Boundary to Keep in Mind
Wings controls Docker workloads and game-server files. Treat its node API and Docker access as administrative infrastructure. Do not expose the daemon or Docker socket directly to the public internet just to make Panel communication easier.
