I recently migrated my Plex from a bare metal Ubuntu install to the linux-server docker image. Now, when new items are added, I’m not getting any poster art or descriptions. I pulled the logs while refreshing metadata. Getting tons of “Error creating directory… File already exists” errors. Checked permissions, my user owns the config directory and all the sub contents. I’m running the container with PUID and PGID = my user.
Most of the errors look like this: ERROR - Error creating directory "/config/Library/Application Support/Plex Media Server/Media/localhost/d": File exists
Ok, the “Media” directory it’s referencing is a symlink to my old media locations that aren’t being used anymore. Why would it be trying to put metadata there?
This is another fine case of why Docker is unnecessary when a perfectly functional host platform package is available. Moving it for the “swoopiness” factor… is it really worth it?
The true test: How often will the Container be exported and moved to a new host where there isn’t an existing native package?
I originally had my Plex server on an Ubuntu VM, but wasn’t able to use the integrated GPU of the intel processor for hardware encoding (a limitation of using a VM). I’m doing a lot of docker for my job so it seemed the perfect opportunity! Currently running 7 containers but I’m sure that will grow.
