container won't start

[ninthwalker]

container won't start

[ninthwalker]

EDIT: I was able to reproduce this error actually by forcing the 'PLEX_SERVER_IP' field to be blank.
The latest version of unRAID and Community Applications plugin allows for a 'required' option on docker variables which I have set for that variable. But older versions may allow for an empty value.

Check to see if you put in the IP address of your plex server and let me know.
Also, what version of unraid/Community Applications are us you using? Thanks.

===================================
A couple things to check for me.
What did you set for the docker template variable 'PLEX_SERVER_IP'? (example, not real info)
Also, did it write any files to your appdata dir?

I tried failing some steps and couldn't reproduce your error yet.

[ironicbadger]

Here is what i put in my docker compose file i use the manage all my containers. ``` nowshowing: image: ninthwalker/nowshowing container_name: nowshowing volumes: - /opt/appdata/nowshowing:/config ports: - 27024:6789 environment: - PUID=${PUID} - PGID=${PGID} - TZ="Europe/London" - PLEX_USERNAME="[email protected]" \ - PLEX_PASSWORD="blah" \ - SMTP_SERVER="smtp.gmail.com" \ - SMTP_PORT="587" \ - EMAIL_USERNAME="[email protected]" \ - EMAIL_PASSWORD="blah" \ restart: always ``` `PGID` and `PUID` are set the the dockeruser of 1050 same as all the other containers i run by LSIO. Your container picks this up fine in the logs and files are populated in the specified `config` directory.

…

On 12 Apr 2017 01:18, "ninthwalker" ***@***.***> wrote: A couple things to check for me. What did you set for the docker template variable 'PLEX_SERVER_IP'? (example, not real info) Also, did it write any files to your appdata dir? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACpQWBz7NuGWcSJrp9Q-jpbYJE-AoxS1ks5rvBhNgaJpZM4M6tf0> .

[ironicbadger]

Also, not using unraid. Debian with docker 1.17ce latest.

…

On 12 Apr 2017 01:18, "ninthwalker" ***@***.***> wrote: A couple things to check for me. What did you set for the docker template variable 'PLEX_SERVER_IP'? (example, not real info) Also, did it write any files to your appdata dir? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACpQWBz7NuGWcSJrp9Q-jpbYJE-AoxS1ks5rvBhNgaJpZM4M6tf0> .

[ironicbadger]

Specified a PLEX_SERVER_IP now and I get a new error Invalid plex.tv credentials which is false. These creds are working via a browser but not via this app. Should I try the plex token instead?

[ninthwalker]

EDIT:
So I messed around with docker-compose. Turns out docker-compose and --env-file read the lines verbatim. So it doesn't like quotes. See this for reference: docker/compose#2854

My working docker-compose.yml file looked like this:

nowshowing:
 image: ninthwalker/nowshowing
 container_name: nowshowing
 volumes:
  - /opt/nowshowing:/config
 ports:
  - 6878:6789
 environment:
  - PUID=99
  - PGID=100
  - TZ=Europe/London
  - PLEX_SERVER_IP=192.168.x.x
  - [email protected]
  - PLEX_PASSWORD=TopSecretP@ssw0rd
  - SMTP_SERVER=smtp.gmail.com
  - SMTP_PORT=587
  - [email protected]
  - EMAIL_PASSWORD=TopSecretP@ssw0rd
 restart: always

to do a quick test of email and web without changing the advanced.yaml or waiting for cron do this:

docker-compose up -d
docker exec nowshowing combinedreport -t

Thanks for letting me know. I think I will add docker-compose and --env-file info to the Wiki section.

==================

So I have not run this from a docker-compose file. I will have to test with that later today.

I've done it with docker run from command line with all the variables and from unraid's GUI template using username or email as plex login creds and it works for me.

The plex username/login is to just get the API plex token.
So if you manually get your plex token and pass that to the PLEX_TOKEN env variable then don't specify the plex username/password it should skip that login part.

[ninthwalker]

Did you ever get around to trying with a new docker-compose file?

[ninthwalker]

Closing this, I'm going to assume some of my suggestions probably fixed your problem. Let me know if they didn't. Thanks.