The most important Docker storage concept on ZimaOS is that a path inside an app container is not the same path the host uses to store the actual data. Plex may see /config and /media, while ZimaOS maps those locations to real folders on a storage drive.
The 2024 tutorial remains conceptually correct. Current IceWhale documentation has expanded the model: users can now set the global App data location under Settings > Apps, move application data to another storage space, inspect per-app volume mappings, and keep large AppData away from the small system drive.
A Container Has Its Own Filesystem
Docker isolates each app from the ZimaOS host. Inside the container, an app sees its own root filesystem beginning at /. Files written only into that disposable layer can disappear when the container is recreated.
Persistent data therefore needs an explicit volume or bind mount to a real host folder.
The Host Path and Container Path Have Different Jobs
A mapping such as:
/DATA/AppData/plex/config → /config
/DATA/Media → /mediameans:
- the left side is the real ZimaOS host location;
- the right side is what Plex sees inside the container.
Plex should be configured to use the container-side path, while backups and host-level file management target the host-side path.
Plex /config Holds Persistent Application State
The source tutorial mapped Plex's /config to an AppData folder so the library database, preferences, metadata, and related state survive container restarts or recreation.
Current ZimaOS still uses the same persistent-data principle, but the actual host path can move if the user changes the App data location.
Plex /media Should Point to the Real Media Library
Plex does not automatically see every disk in ZimaOS. A host media folder must be mounted into the Plex container and then selected from the corresponding container-side path.
App Settings Show and Edit the Volume Mappings
Zima-Giorgio's tutorial told users to open Plex Settings and inspect the volume paths. Current ZimaOS keeps this model and also provides broader app-storage visibility through Settings > Apps.
Use the current ZimaOS app-storage path model for present-day path behavior.
Current ZimaOS Lets You Move the Global App Data Location
IceWhale now recommends pointing App data location at a real storage space instead of filling the system drive. ZimaOS can move managed app data when that location is changed.
This means a hard-coded 2024 path such as /DATA/AppData/plex/config may not be the literal path on every current system.
Back Up the Host-Side Persistent Folders
When backing up Plex, protect the host folder that stores /config and any other important persistent mounts. Backing up the disposable container image is usually less valuable because the image can be pulled again.
For databases, consider whether the application needs to be stopped or exported consistently before a filesystem-level backup.
Media and AppData Are Different Storage Classes
Plex configuration may be only a few gigabytes while a media library may be tens of terabytes. They can live on different storage spaces and have different backup policies.
Do not move the entire media library just because you change Plex's AppData location.
A Correct Mapping Can Still Fail Because of Permissions
If Plex can see the mounted path but cannot open files, the next layer is filesystem ownership/permissions. If the path does not exist inside the container at all, fix the volume mapping first.
Docker Path FAQ
Should Plex use the ZimaOS host path in its library settings?
No. Plex should normally use the container-side path such as /media.
Does deleting a Docker container automatically delete mapped AppData?
No. Persistent host folders remain unless they are deliberately removed.
Is /DATA/AppData always the current physical AppData location?
Not necessarily. Current ZimaOS lets users choose and migrate the managed App data location.
