The --tmpfs flag is a huge win for applications that use containers as unit of work processors.
In these use cases, I want to start a container, have it process a unit of work, clear any state, and start over again. Previously, you could orchestrate this by (as an example, there are other ways) mounting a tmpfs file system into any runtime necessary directories, starting the container, stopping it once the work is done, clean up the tmpfs, and then start the container again.
Now, you can create everything once with the --tmpfs flag and simply use "restart" to clear any state. Super simple. Awesome!
In these use cases, I want to start a container, have it process a unit of work, clear any state, and start over again. Previously, you could orchestrate this by (as an example, there are other ways) mounting a tmpfs file system into any runtime necessary directories, starting the container, stopping it once the work is done, clean up the tmpfs, and then start the container again.
Now, you can create everything once with the --tmpfs flag and simply use "restart" to clear any state. Super simple. Awesome!