Puppy Linux Discussion Forum

Hi,

I'd like to run several programs in which I have low trust (like Telegram client) in a container.

It seems that the Daedalus container cannot provide persistency that would allow to save session information, so that an user wouldn't have to associate devices or enter credentials every time the container is started.

This could be done with a virtual machine, but would be great if we could have a different kind of containers: persistent containers.
Much like what happens with lxc/lxd/incus.

There's an use case for both types of containers: non-persistent and persistent.
Maybe it doesn't request a lot of work to implement and would give an extra appeal to EasyOS.

Containers do save session information.

They have a .session folder, just like the main filesystem.

For example, /mnt/wkg/containers/daedalus/.session

While daedalus is running, the session is in /mnt/.easy_rw/daedalus

When session is saved, at shutdown or via "save" icon, that gets flushed to /mnt/wkg/containers/daedalus/.session

At least, that is what is supposed to happen.

If you are setup not to run in RAM, then session will be written direct to /mnt/wkg/containers/daedalus/.session