Replies: 1 comment
-
@poweribo I ran into this same issue and the solution is pretty straightforward, although not obvious given the dagster documentation. The dagster_run_launcher.py file leverages the docker module to create and run the containers. The containers are created using the create method of the container class:
In your dagster.yml file you can specify the contents of container_kwargs you see above which will be passed into the create method. One of the arguments the create method takes is "auto_remove: bool". So you can simply set the "auto_remove: True" key/value in your dagster.yml file.
If you already figured this out, excellent! Perhaps someone else can benefit.... |
Beta Was this translation helpful? Give feedback.
-
How do you make sure the generated docker containers for every run gets cleaned up after? I've noticed Dagster uses up a lot of space after a few weeks of run. we have more than a dozen jobs running from 15mins, daily to weekly. We manually run docker prune right now but is this what others do? Does Dagster actively cleanup unused docker containers?
Beta Was this translation helpful? Give feedback.
All reactions