Manual Compose Editing Bypassed ZimaOS-Managed Variables
A new ZimaOS user manually edited Jellyfin's Compose file to change storage paths. After restarting, Compose warned that PGID, PUID, TZ, and AppID were unset, and several hardware device mappings did not behave as expected.
The community reply explained that ZimaOS normally injects those values through its app-management layer. Editing the generated YAML outside that workflow can leave placeholders without the environment ZimaOS expected to supply.
Change Storage Through App Settings and Volumes
The recommended path was to open the Jellyfin App Settings and modify its volume mappings there instead of rewriting the Compose file. ZimaOS can then retain the application metadata, environment variables, and device entries while applying the chosen host storage paths.
The author later confirmed that this method worked. Once the correct secondary-drive paths were selected in App Settings, Jellyfin ran properly without the manual Compose workflow.
Reinstalling Restores the Store-Supplied Configuration
If the generated configuration has already been extensively changed, the reply proposed removing Jellyfin from the dashboard and reinstalling it from the App Store to restore the original defaults. Existing application data must be preserved through correct host-volume mappings before removal; reinstalling a container is not a substitute for backing up its configuration.
A manual repair remains possible only if every missing variable and required device path is defined correctly. The thread favored the ZimaOS settings interface because it reduced the chance of dropping managed values.
Proxmox Disk Mapping Was a Separate Complication
The author was running ZimaOS as a virtual machine under Proxmox on Debian 13. A disk passed with a qm set command and a stale /etc/fstab mount caused maintenance-mode problems after reboot. ZimaOS also named the device differently than the user expected.
That virtualization issue was separate from the missing Compose variables. The working result required both a stable VM disk mapping and correct Jellyfin volume paths in the ZimaOS app interface.
The Later NTP Question Was Not Part of the Jellyfin Fix
The thread moved on to time synchronization after Jellyfin was working. NTP behavior on the Proxmox host and guest did not cause the Compose warnings, so it should be diagnosed independently.
FAQ
Why did PUID, PGID, TZ, and AppID become blank?
The warnings appeared after manual edits bypassed the values normally managed by the ZimaOS application layer.
Where should Jellyfin storage paths be changed?
The confirmed solution was to use Jellyfin's ZimaOS App Settings and volume controls.
Did the missing hardware devices require new drivers?
The thread did not establish a driver failure. Restoring the managed app configuration and volume paths resolved the author's Jellyfin setup.
