Plex docker startup takes forever

Plex Media Server NAS & Devices
1

Server Version#: 1.19.4.2902
When starting the docker the following shows up in logs:

      _         ()
     | |  ___   _    __
     | | / __| | |  /  \
     | | \__ \ | | | () |
     |_| |___/ |_|  \__/

Brought to you by linuxserver.io

To support LSIO projects visit:
https://www.linuxserver.io/donate/

GID/UID

User uid: 998
User gid: 100

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 40-chown-files: executing…
Change in ownership detected, please be patient while we chown existing files
This could take some time

and then it is another ± 10 min before I can access plex:

[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 45-plex-claim: executing…
[cont-init.d] 45-plex-claim: exited 0.
[cont-init.d] 50-gid-video: executing…
[cont-init.d] 50-gid-video: exited 0.
[cont-init.d] 60-plex-update: executing…
Docker is used for versioning skip update check
[cont-init.d] 60-plex-update: exited 0.
[cont-init.d] 99-custom-scripts: executing…
[custom-init] no custom files found exiting…
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.

I’m running the docker as admin and have tried root but both do a chown on startup is there anyway to stop it from happening?

2

If the user that the container ran as was the same user as the owner of the media files, the chown rampage Plex is doing wouldn’t need to happen.

Running a docker as the root user is a bad idea unless this is explicitly required by the container and the documentation would tell you this.

See: https://support.plex.tv/articles/200288596-linux-permissions-guide/

3

Linuxserver.io has their own support system:
https://discord.gg/YWrKVTn

Their docker has basically not much to do with plex. They also know their setup best.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.