Lost on docker and plex

General Discussions
1

I admit I’m lost lost lost.
I installed docker fine.
I read the Official Plex Media Server Docker Images - Getting Started

It seems I have to create a plex container. (I’m on linux mint 18.3)

In terminal I pasted:
sudo docker create
–name plex
–network=host
–restart=always
-e VERSION=latest
-e PUID=1001 -e PGID=1001
-e TZ="America/New_York
-e PLEX_CLAIM=“blablabla”
-v /disks/4T/config:/config
-v /disks/4T/transcode:/transcode
-v /disks/4T/Series:/data \TVshows
-v //disks/4T/Movie_Database:/Movies
linuxserver/plex

I ended up at prompt

instead of the usual linux prompt. I had to CTL+C to get out.

not sure if I had to do this since at some point in this mess I pulled an image of a plex container

Anyway when I execute the command
docker run linuxserver/plex

I get:

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 10-adduser: executing…
usermod: no changes

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

Brought to you by linuxserver.io
We gratefully accept donations at:
Donate | LinuxServer.io

GID/UID

User uid: 911
User gid: 911

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing…
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing…
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing…

#######################################################

Update routine will not run because you havent set

the VERSION variable or you opted out of updates.

For more information checkout :-

GitHub - linuxserver/docker-plex

#######################################################

[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting dbus-daemon
Starting Plex Media Server.
[services.d] done.
Starting Avahi daemon
Found user ‘avahi’ (UID 102) and group ‘avahi’ (GID 103).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
No service file found in /etc/avahi/services.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.2.
New relevant interface eth0.IPv4 for mDNS.
Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
New relevant interface lo.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 172.17.0.2 on eth0.IPv4.
Registering new address record for 127.0.0.1 on lo.IPv4.
Server startup complete. Host name is 0085441c4f50.local. Local service cookie is 1081402980.
Error in command line:the argument for option ‘–serverUuid’ should follow immediately after the equal sign
Crash Uploader options (all are required):
–directory arg Directory to scan for crash reports
–serverUuid arg UUID of the server that crashed
–userId arg User that owns this product
–platform arg Platform string
–url arg URL to upload to
–help show help message
–version arg Version of the product

so what’s going on here???

2

I’d suggest you look into a docker GUI to help you get this deployed.

https://blog.codeship.com/docker-guis/

I use unraid that has a nice web gui to manage my docker containers.
This will walk you through things and has some basic syntax checks to make sure you do not shoot yourself in the foot.

just off the bat

-v /disks/4T/Series:/data \TVshows

You have a wrong \ it should be /
you also have 2 // in //disks/4T/Movie_Database:/Movies but that may not be an issue.
did you check that UID1001 and PGID 1001 is correct for your system?

Also id suggest you just add /disks/4T as /data instead of movies and series and transcode separate this way in the future when you want to add /music you don’t need to add a whole no directory as all would be housed under /disks/4T/

3

Thanks a GUI would be so helpful.

Yup, I see the typos. 5 hours in and those things become a blur.

thanks again

edit: the gui’s from that page were confusing simply because I had no experience with docker until I installed it 12 hours ago. That was also my problem. Your pointing out my mistakes helped a great deal. Also reading a few more how-to’s and combining information from them all finally solved the problem. Too many of them assumed to high a level of working knowledge of docker and it’s commands. It’s all good now.

4

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