On Fri, Mar 9, 2018 at 10:17 AM, Alec Warner <[email protected]> wrote:
> The containers are nominally stateless, so there is less chance of 'gunk'
> building up and surprising me later. It also makes the lifecycle simpler.
>
> Obviously its somewhat harder for stateful services (databases, etc.) but I
> suspect things like SANs (or Ceph) can really provide the storage backing
> for the database.
> (database "schema" cleanliness is perhaps a separate issue that I'll defer
> for another time ;p)
>
Restated:
Containers are stateless, which prevents programs from munging state,
because there is none. This is okay except when one needs state, which
one does for most desktop activities.
This implies it doesn't solve the problem. Working around it may be
valid, but only if state can be preserved.
Cheers,
R0b0t1
