Remove .config-lock on start? about docker-flexget HOT 5 CLOSED

I've definitely run into this issue before myself, however, I'm not sure how to fix this. As far as I know Docker doesn't have a way to run a command before (or after) starting/restarting a container.

The only way I can think of to do this would be to change the CMD line in the Dockerfile to something like:

CMD ["rm", "-f", "/etc/flexget/.config-lock && flexget", "&&", "flexget", "-c", "/etc/flexget/config.yml", "--loglevel", "verbose", "daemon", "start"]

However, this would totally break the single process nature of Docker and I'm not even sure that would work. If you have any other ideas please share.

In the event this does happen to you though you can solve it like so (assuming you followed the README and named your containers/volumes the same):

1. Stop the container

docker stop flexget-client

2. Remove the .config-lock file from the volume

docker run -it --rm -v flexget-data:/etc/flexget phlak/flexget phlak/flexget rm /etc/flexget/.config-lock

3. Start the container.

docker start flexget-client

from docker-flexget.

Using a bash script which deletes the file before launching Flexget doesn’t break single process of Docker since it won’t run simultaneously, and I think this is a totally fine way of solving it. Would be better with an option in Flexget itself though, but that might be more of a hassle to implement.

from docker-flexget.

@PHLAK Seen that Flexget themselves recommend removing the lock file on start? https://flexget.com/InstallWizard/SynologyNAS/Docker

from docker-flexget.

Good to know @oscar-b, also leaving this here as a note for myself: https://stackoverflow.com/a/41518225

from docker-flexget.

Resolved with 84449dc

from docker-flexget.