Open FredrikM97 opened 4 years ago
Is there something in /config/traktarr.log? Try starting the container with another ENTRYPOINT, like you add: ENTRYPOINT=/bin/sh to get a shell, and then launching traktarr manually with the original endpoint, described in the docker file
I ran into the same issue,
I think that's because the entry point in the Dockerfile is
python trackt.py
which immediately quit after outputing the help, therefore the container stop, because you did not provide any interactive mode or tty.
So either you run the container in an interactive way and start a command inside,
or you can use
python trackt.py run --run-now
as an entrypoint
this can be setup in the docker-compose.yml without touching the Dockerfile (and therefore you can still used cloudb0x/traktarr image
it should be something like
traktarr:
image: cloudb0x/traktarr
entrypoint: python traktarr.py run --run-now
network_mode: host
container_name: trakt-tv
environment:
- TRAKTARR_CONFIG=/config/config.json
- TRAKTARR_CACHEFILE=/config/cache.db
- TRAKTARR_LOGFILE=/config/traktarr.log
volumes:
- /opt/appdata/traktarr:/config
cap_add:
- NET_ADMIN
restart: always
Like the title describe the container is stuck in restarting in the latest version of traktarr. Expect the system to stay on "Up" so I can attach it and start writing commands but the container keeps restarting.
Download container from cloudb0x/traktarr Create the config file at volume destination /config Check status using docker-compose ps Check logs using docker container logs [container]
Settings: