[question] Does Tork remove docker images that are not used for a long time?

[arturo32]

My use case is the following:

I'm using Tork (v0.1.144) as a Go library in standalone mode inside a container with docker compose (with postgres in the same docker network).

I'm binding the docker daemon inside the container with the host docker daemon where the tork container is running. I build manually a docker image in the host machine and them Tork can access it and run it in tasks as a "brother container". Everything is great.

Then, after some days where I do not use the server, my manually build image is gone. Every HTTP request then returns 400. Does Tork periodically remove unused images? I thought it was Docker itself first, but I couldn't find anyone having this problem on the internet.

[arturo32]

Is this related?

https://github.com/runabol/tork/pull/560/files

[arturo32]

Ooooh.... How to I set this to like.. never? Or is there a better option?

tork/configs/sample.config.toml

Line 127 in c0da803

image.ttl = "24h" # Time-to-live for cached images since their last use

[runabol]

Yep. You got it. That’s the config. I could probably addd an option to turn it off entirely.

[arturo32]

Yep. You got it. That’s the config. I could probably addd an option to turn it off entirely.

That would be ideal! For now, for me, there's no hurry because I put, like, 100k hours in the config file haha.