Restarting a watcher container requires re-validating the license.

[BrianAllred]

This is especially cumbersome because I use watchtower to keep containers up to date. If watchtower restarts the container automatically due to an update, then my files will stop processing.

[BrianAllred]

Actually, looks like the /data directory wasn't consistent between when watcher was running (/data/filebot) and when I input the license (/data). Confusing, but fixable.

[rednoah]

Presumably, you're sometimes running the filebot process as user 1000 named filebot, and sometimes as user 0 named root. Each user has its own $HOME folder because you would run into permission issues if different users create / read / write files in the same folder. Files created by root are particularly problematic for normal users.

Please read How do I activate my license? for details:

If you use -e PUID or -e PGID to run filebot with a different UID then you must use the same -e PUID or -e PGID environment variables when calling filebot --license to install the your license key into the correct user-specific application data folder.