Jackett fails to startup

[greenfrogsb]

Jackett fails to startup

[garciaErick]

I have found out in my logs this happened after the following update

04-30 00:09:08 Info Checking for updates... Jackett variant: CoreLinuxArm32 04-30 00:09:08 Info New release found. Current version: v0.17.954 New version: v0.17.960 04-30 00:09:08 Info Downloading release v0.17.960 It could take a while... 04-30 00:10:00 Info Starting updater: /tmp/JackettUpdate-v0.17.960-637553381652563292/Jackett/JackettUpdater --Path "/app/Jackett" --Type "Console" --Args " --NoRestart" --KillPids "11555" --NoRestart 04-30 00:10:00 Info Updater started process id: 19860 04-30 00:10:16 Info Jackett Updater v0.17.960

[garciaErick]

Seems this was caused by a faulty update, deleted the container and ran deploy.sh again, is there any way this can be avoided?

[GreenFrogSB]

There are two independent ways of stopping container from updating.

1. Lock docker compose file to specific container version - all containers are by default set to pull latest version down for deployment. This wont be changed globally as this is desired behavior for the script also, I would like to avoid manual versioning if possible. You can lock particular container to specific version by changing docker-compose files locally. This way redeployment will always bind version you selected.
2. Even if above is locked by compose file container itself has a mechanism allowing it to be updated over UI, this potentially can be disabled or never executed - these settings are specific to each container, look under settings and updates if there are any option there.