4 ms·
Besides faster start time, one use case would be state persistence. If you have a process that writes stuff to a file inside a container (not in a volume or mo
by bheadmaster 4y ago
Besides faster start time, one use case would be state persistence.
If you have a process that writes stuff to a file inside a container (not in a volume or mounted path), stopping a container without destroying it doesn't delete the modifications. Starting the container again may allow the process to read the contents of the file, possibly continuing its execution from some checkpoint.
- WolfOliver 4y agoins't this an invitation to screw up your app design?
- WolfOliver 4y agoI mean starting and stopping a container won't work anymore if you use a container orchestration layer (e.g. K8s).
- bheadmaster 4y agoYeah. But I suppose it can be used for some basic caching, as long as it's properly implemented. Like some LRU layer over SQLite.