The only thing persisting in a docker container is the filesystem, and that's only until the container is killed (not just stopped). Containers are generally m

The only thing persisting in a docker container is the filesystem, and that's only until the container is killed (not just stopped). Containers are generally meant to define an initial fs image and then be more or less ephemeral (`docker commit` being a thing virtually unseen in the wild). Smalltalk images persist the state of the whole runtime, typically automatically. There's some overlap for sure, but I don't think one subsumes the other.