FileBot

Hello

I upgraded today to a new Synology NAS and I've tested the container version of Filebot.
Everything works well but everytime I launch a new filebot instance, a randomly generated "adjective_name" container appears in Docker list, I got for instance a priceless_hamilton, a stoic_agnis, ...
These new containers do not disappears when the task is completed.

Is this normal? Is there a way to automatically cancel them once finished?

Thanks

cico wrote: ↑26 Apr 2019, 13:59 I upgraded today to a new Synology NAS and I've tested the container version of Filebot.

What container version?

I recommend using the Synology packages if you're using Synology:
viewtopic.php?f=13&t=1802

rednoah wrote: ↑26 Apr 2019, 16:44
What container version?

I recommend using the Synology packages if you're using Synology:
viewtopic.php?f=13&t=1802

I've installed it yesterday choosing latest as version
hub.docker.com says it has been updated 7 days ago

I see, so you're using the official Docker containers:
https://hub.docker.com/r/rednoah/filebot/

What's the docker command-line call you're executing?

Are you setting the --rm flag?
https://docs.docker.com/engine/referenc ... an-up---rm

rednoah wrote: ↑27 Apr 2019, 08:15
Are you setting the --rm flag?
https://docs.docker.com/engine/referenc ... an-up---rm

I was not! I now added it to my scripts and they work perfectly!
Thank you indeed rednoah

Just FYI, I started from the command line on your docker page which is not reporting the --rm option. Maybe you want to add it so save the newbies like myself