Posts by aptalca

It could be a number of things. Your media may not be named in the style Plex likes it so it may be having issues identifying. Or you may have been having internet connectivity issues and requests may have been timing out, or you may have been getting throttled by the metadata provider.

The one thing I can think of with regards to usb drives is that flash drives usually have pretty awful write speeds. Plus, plex libraries can grow to hundreds of thousands of files easily and to hundreds of gigabytes (especially if you turn on video preview thumbnails). I really wouldn't recommend hosting the Plex library on a flash drive.

With that said, there are no issues with the Plex docker container. Many people use with very large libraries (on ssds mostly) and scans are fairly quick.

Are you trying to create a volume or do a bind mount? You need to specify that on portainer

The library and the settings are all under the /config folder. So it depends on what folder you set it to in addon settings. By default it is under the addon_data folder on your main storage (usb drive).

Quote from Borygo77

aptalca I need you help I'm afraid

‘filesystem_check_changes’ => 1, This option isn't working for me for some bloody reason and I'm after setting up everything like 10 times.

I know there is other option to trigger files:scan with occ but can't get that as well can you write me a line I could put to the cron to scan files from time to time please ?

My data and config is in /storage/NexT without subfolders.... Really pulling my hear on it three days in a row

Thank you in advance.

I don't use nextcloud so I have no idea what that is. Ask on our discord or GitHub

Great to hear. I'll do the same with the other addons that use data folders like plex and emby

Quote from FeFiFoFum

(My emphasis on a few lines there)

I'm having precisely this problem with mine, I've just started using LibreElec, I'm so very very impressed so far, but stuck at this point, identical issues. (I use SMB, not NFS)

My SMB pointers in my XML file, in Kodi, which are obviously working for Kodi - as soon as I configure them to be the 'redirects' for Plex in the Plex config, will stop the Plex docker executing and running.

I can confirm this by SSH in, then typing in

docker image ls

and

docker container ls

The container is pulled down, but it's not running, unless I reset those settings to default, then it's listed as running.

So what's the easy solution?

Display More

Did you read the answer and how it was solved in the next post?

You cannot use nfs:// or smb:// locations as mount points with docker. You need to mount those smb locations on LE first and use those locations

You might be better off running LE in a VM with a gpu passthrough if consolidation and sandboxing are the primary motivators

Yup, you can include as many "-v" directives as you like

Quote from vpeter

One option is to add local share in /storage/.kodi/addons/docker.linuxserver.nextcloud/bin/docker.linuxserver.nextcloud

Code

-v /storage/downloads/test3:/test3 \

and this folder has nobody:users permissions.

And I added /test3 under External storages.

vpeter just a heads up, I got a PR for the nextcloud addon awaiting review that will add a text field in the addon settings where you can add your line "-v /storage/downloads/test3:/test3" so no need to modify addon files and no need to worry about updates reverting your changes

add optional docker parameters to nextcloud for additional mount points by aptalca · Pull Request #47 · linuxserver/libreelec-addon-repo · GitHub

You need a webserver to do that redirection. Letsencrypt would be the ultimate way, but you can also do it with nginx.

I've been meaning to add an "extra parameters" setting where users can add any additional docker parameter like extra ports or mapped folders etc. when needed.

I'll do that today or tomorrow and then you can add the additional folder mount.

Vpeter's solution works, but would be removed if the addon is updated or reinstalled

Quote from Borygo77

The thing I want to do is mount /storage/videos/ as external drive with local option choosen from tab. It wont let me

Here it is folder /storage/pictures owned as nobody:users and cant mount it as local drive

The docker container doesn't know where /storage/pictures is. It only knows the folders that are mapped. If you go into the addon settings, you'll see that there is a mapping for /data and you pick a folder for it on libreelec. That libreelec folder gets mapped to /data inside the container so nextcloud only sees /data.

So pick a location where you want your data to be stored, and select that location in addon settings, /data mapping. Then in nextcloud, you'll find that location as /data

Find what out?

The addon automatically sets the correct permissions on the data folder: libreelec-addon-repo/docker.linuxserver.nextcloud at master · linuxserver/libreelec-addon-repo · GitHub

If you're mounting an external drive, make sure that the files are owned by nobody:users

Quote from Fenderman

How does that work?

I don't follow

Nextcloud runs as user nobody and the permissions should be set for that user on that mount

Here's the service file:

LibreELEC.tv/kodi.service at master · LibreELEC/LibreELEC.tv · GitHub

That's way beyond the scope of this addon

Quote from robeen

Thanks for your reply and pointing this out.

Automatic updates is and should be disabled after this and whenever you want it updated it's actually not a big thing to fix manually.

It is mounted with proper UID but as RO indeed.

In my opinion though, doing chown -R here without a warning is both risky and pointless. And with a large archive mounted over a network it delays the startup with minutes and possibly hours. Finally, any existing ownership and group-access structure will be completely destroyed.

However, now everything is working properly and I'm very pleased with it. Kodi still as the main player and Plex for streaming services.

Maybe one thing, It would be nice and perhaps more "clean" to have a custom folder in addition to videos/tvshows/pictures. This as a mounted target may contain a mix of all those plus more.

Display More

Risky, perhaps, but pointless it is not. Chown on media files is a necessary evil here. This is a plugin that people expect to just work.

The default folders are the local folders on LE that are normally owned by root. But docker containers run as user nobody. We need to make them readable. I suspect most people using this plugin are hosting their media on a usb drive attached to LE. That's why we're not getting complaints about the chown.

The concern about the time it takes is valid. We can perhaps stat the top folder and chown only when necessary.

An alternative is doing a chmod -R go+r which would still cause issues with remote mounts.