You change to the stack does nothing, as :latest is assumed automatically, if you do not specify a tag. To check if a new image is available, use the pull image option in portainer.
I know. I also wrote it in the initial post.
If you last your config, you messed with the volumes or did not provide any volumes so the config gets lost every time you restart the container.
Check the docs of your docker image.
Those inserted are only the first part of the yaml files that I use.
Obviously, if you don't insert the volumes, nothing can work
I used that previously.
But it gave me a lot of problems that the official release doesn't give me
Maybe if I paste it here you will actually read it?
I had already read it gderf .
The fact is that, having a Plex Pass, I had chosen to install with :latest tag for convenience.
In the first installation I omitted the tag because I know that if no tag is specified by default the container uses the :latest tag.
Do you advise me to change tag?
Should I use the tag :plexpass?
You should read the documentation for the image you linked to. If the proper Tag is usedI use the Official Plex Media Server Docker Repo all that is necessary to check for and install the most current version of Plex is to restart the container.
That's exactly what I did gderf !
I use the Official Plex Media Server Docker Repo.
I went to check the tags and saw that the latest tag had been added.
So I edited my yaml file from:
and I restarted the stack.
Nothing has been updated, I just lost the previous configuration!
This evening opening Plex I found the following message.
I went to check on https://hub.docker.com/r/plexinc/pms-docker/ and noticed there was an update from 16 hours ago.
I modified my yaml file by inserting the tag :latest (I know, it wasn't necessary ...) and I restarted the stack.
Now, apart from the fact that I have lost all configuration, the version has not updated.
I also read the post How to update Plex Media Server with Portainer but I believe I have done the correct steps.
How should I upgrade it?
Are you transferring a large file?
Is your client and OMV both connected to ethernet?
What Hardware is OMV? If you're using a slow CPU system like an old RaspberryPI, you might have to tweak some SMB settings.
Monitor OMV server performance when copying a file.
- I usually transfer multimedia files (photos, videos, music) ranging from 1 Mb to 25 Mb.
- Client (Windows 10) and OMV are connected via ethernet by switch D-Link DGS-1005D (5 port Gigabit 10/100/1000 Mbps)
- OMV use an AMD Phenom II X4 940 processor
- In attach is the log obtained with the following command iperf3.exe -c 192.168.xxx.xxx -P 50 -fg -t 5 launched from the Windows 10 PC with OMV listening as a server (log taken from OMV after command iperf3 -s)
With OMV WebGui I have created a SAMBA share, but the transfer rate does not improve...
Can anyone help me to write an optimal configuration?
I think there are some problems with one or more steps during the preparation/configuration.
In my NAS i had created a user called "docker" with R/W permissions in 2 folders called "AppData" and "Media"
Inside "AppData" i had stored all the necessary for every container.
Inside "Media" i have photos, films, etc...
With the terminal (like Putty), just type:
For the PUID and the PGID necessary for the compose
Then, i had created the container starting with:Code
You can deploy the compose with Portainer, inside the tab called "Stacks", or inside the terminal with docker-compose.
For example you can save the code (with the correct parameters) above inside Notepad with the name docker-compose.txt, then you need to rename the file in docker-compose.yml.
Copy the file inside your NAS, in a folder called (in this case) plex.
From the terminal, go inside the folder and type:
docker-compose up -d
That's exactly what I did Thormir84
The only thing different is that I hadn't set ACLs on the folders.
I will also perform this setting and reinstall.
At this point I would delete any config files that have been created and follow the suggestions posted by raulfg3 and Thormir84 and use Portainer, create a stack then deploy the container. If this procedure errors the same as your Yacht install then the issue is related to the drives within the array.
Exactly what I did geaves
In addition, I moved the /config folder from the RAID to another HD present in the OMV system.
Now let's see what happens
Now I have tried to change the location of the /config folder by moving it to another disk.
Let's see what happens...
Plex reinstalled as you suggested.
Everything seemed to work correctly but this morning, at restart, RAID system was not mounted as it had in the previous days (see >> HERE <<).
I then ran the fsck /dev/md0 command again and once again a multitude of errors within the Plex /config folder.
I proceeded to fix all errors and then reboot the system.
The Raid system was mounted correctly but the initial Plex configuration is completely gone and I was forced to a new initialization...
In the end it is very simple:
use folders for storage of the media created as shared folders in the GUI of OMV
use a user that is created as user in the GUI of OMV
and it just works
macom exactly what I meant and did.
I have given at the new user read and write permissions for all new shared folders that I will use for Plex (/config, /plexmedia and /transcode).
All (users and folders) were created with OMV WebGUI.
And permissions too.