Bottom Line: Emby Auto-Organize Needs Both a Writable Docker Mount and Writable Host Permissions
Emby can scan a media library with read-only access, but Auto-Organize must rename, move and sometimes delete files. That requires write access at two layers: the ZimaOS host folder must be mounted into the container as read/write, and the Emby process must have permission to modify the host files. Fix both deliberately; do not use recursive chmod 777 as the permanent solution.
Step 1: Confirm the Host Folder Is Mounted Read/Write
Open the Emby app settings and inspect Volumes. A mapping should look conceptually like:
/media/RAID5/TV -> /media/tv
Inside Emby, select /media/tv. Emby cannot browse the left-hand ZimaOS host path directly. Docker's Docker bind mounts explains the two-path model.
The current ZimaOS app paths applies to App Store containers in general.
Step 2: Prove the Mount Is Not Read-Only
docker inspect EMBY_CONTAINER
Look for the TV/media bind mount and confirm it is not marked read-only. You can also test from inside the container with a harmless temporary file in the exact mapped destination:
docker exec -it EMBY_CONTAINER sh
touch /media/tv/.emby-write-test
rm /media/tv/.emby-write-test
If touch fails, Auto-Organize will fail too.
Step 3: Match the Emby Process to Host Ownership
Check the host folder and the process identity:
ls -ld /media/RAID5/TV
ls -ln /media/RAID5/TV
docker exec EMBY_CONTAINER id
Then grant the minimum ownership/group permission required by that container. The old reply suggested chown -R 1000:1000, but UID 1000 is not guaranteed to be the identity used by every Emby image. Verify first.
Emby's Emby Docker setup is the upstream reference for the image you run.
Do Not Use chmod -R 777 as a Permanent Fix
If 777 makes the feature work, you have proven a permission problem—but you have also granted every local user/process write access. Restore a narrower owner/group model once the test is complete. For a media server, 775 with the correct group is usually safer than “everyone can write,” but the exact values depend on how your container identity is configured.
Keep Source and Destination Paths Writable
Auto-Organize may watch an incoming folder and then move files into the final TV library. Both locations must be visible inside the container, and the destination needs write access. A read-only final library can make the watch folder appear healthy until the first rename/move operation.
RAID 5 Is Not the Permission Layer
The media living on RAID 5 does not inherently prevent writes. RAID controls redundancy and block storage; Docker bind mounts and filesystem ownership control application access. Do not rebuild the array because a container receives Permission denied.
The ZimaOS data migration is useful when media paths were moved after the Emby container was created.
Back Up Emby Configuration Before Recreating the App
Reinstalling Emby can change container settings without fixing the underlying media folder. Preserve the persistent Emby config and document all volume mappings before recreation. The ZimaOS backup covers the recovery layer.
A Safer Permission Troubleshooting Order
- Verify host path exists.
- Verify container path maps to it.
- Verify mount is read/write.
- Verify container UID/GID.
- Verify host ownership/group.
- Test one temporary file.
- Only then test Auto-Organize.
The ZimaOS app requirements provides the broader App Store storage model.
FAQ
Why can Emby play files but not organize them?
Playback only needs read access. Auto-Organize needs permission to create, rename, move and delete files.
Should I chown the folder to 1000:1000?
Only if the running Emby process actually uses that UID/GID. Check the container identity first.
Is chmod 777 safe?
Use it only as a brief diagnostic if necessary. It is too broad as a permanent permission model.
Does RAID 5 make Emby read-only?
No. RAID level and application file permissions are separate layers.
Which path should I add inside Emby?
Use the container-side path from the Docker volume mapping, not the host path shown in ZimaOS Files.
