I have never heard of the Plex docker using a port conflicting with avahi-daemon. How did you determine that this was the case?
Beiträge von gderf
-
-
Without knowing what hardware you are running this on, and without seeing the container configuration, and without seeing the container log, not much help can be offered.
-
Your data drives are mounted in /srv with unique directory names as the mount points. That's where.
-
/media is not a good choice. That directory is on the root file system and if you start placing a lot of files there you will eventually run out of room on that drive and things will break.
-
Start looking in /srv
This is one of the reasons I don't use /sharedfolders in docker volume and bind mounts. If you don't know where the files and directoryies really are, you can't determine their ownership and permissions. And if those are wrong, you aren't going to get anywhere.
-
Correct ownership alone is not enough. What are the permissions?
-
What are the ownership and permissions on the chroot, starting with the drive mountpoint and going deeper to the chroot?
-
If you don't see any plugins at all, something is wrong with your installation.
You might try:
apt-get install --reinstall openmediavault
-
Only one update process at a time can be run. That's why you are getting that lock error.
Try rebooting.
-
Try running:
apt-get -f install
And see if it fixes anything.
-
-
-
-
-
Are you saying you have no idea where you stored all the media files you wish to serve with Plex?
Did your media files exist on any of your hard drives before you created any shared folders?
-
-
There is no Emby plugin available.
Run it in a docker if you still want it.
-
First, are PUID and GUID a real user and group on your machine?
You set /config to /sharedfolders/Appdata/plex but where is /sharedfolders/Appdata/plex on your system? What is the real physical directory? Does the user you specified in PUID have read and write permissions on that directory?
Yes, that's what I mean by not using shared folders.
The top two causes of docker problems around here are incorrect networking specifications for the container and incorrect filesystem ownership and permissions on the filesystem outside the container.
Networking problems are almost completely avoided by running containers in Host networking mode which almost always just works all by itself. Running a Bridged networking connection means you set the entire thing up by hand where every thing you specify might be a mistake or might introduce an incompatibility.
Not much can be said about filesystem ownership and permissions other than they must be correct or the container will not be able to communicate with the disk(s) in the machine.
A more subtle problem has to do with relativity. When you specify directorys and files within a program running inside the container, all those references must be on and along the Container paths, not the absolute filesystem locations outside the container.
When you tried to add a Library in Plex and went looking for the /sharedfolders but didn't see it, the reason is that the container is running as a user that does not have read permission on either the sharedfolder or the directory referenced by the shared folder.
-
You do not want any Plex Volumes and Bind mounts created within the container.
For Plex running in a docker you need to setup the Volumes and Bind mounts external to the container yourself, and from within the Plex interface you have to configure your media locations as the Container paths when you define your Librarys.
-
Most likely explanation for your troubles is that the user the containers run as does not have adequate permissions to access the shared folders and/or the the actual file systems directories on the disks. Check these very carefully.
Be advised that setting Privileges and/or ACLs in the OMV Shared Folders panel is not the same thing as setting file system permissions. And it's the latter that are vitally important.
I never make any Privileges and/or ACL settings in the OMV Shared Folders panel.
The easiest way to avoid problems like this is to NOT use Shared Folders in docker Volume and bind mount settings. Use the actual filesystem locations instead, but only after you are sure the permissions on those filesystem locations are correct.