[FEAT] What is the best way to make all changes permanent like on KASM?

[nvroot]

Is this a new feature request?

• I have searched the existing issues

Wanted change

Thank you for your work on this project. As mentioned previously, the container run with proot functionality, which seriously increases security but resets all changes after reboot - currently only preserving the /config directory while everything else is lost on restart.
Could you please advise the recommended method to persist all system changes permanently? This would include:
Installed packages and programs
System configuration files (in /etc, /usr, /var,/.config, ~/ etc.)
User data and settings (including /root)
So at end of the day we can also use pull_policy: always, container sign and verification of signature to prevent all unwanted changes too.

Reason for change

Requires partial reconfiguration after each session (some tools need manual setup that cannot be automated with CI)
Disrupts established workflows (many tools require persistent custom configurations)
Adds unnecessary overhead for security testing env.

Proposed code change

No response

[j0nnymoe]

You can either write custom start scripts using this: https://docs.linuxserver.io/general/container-customization/
or I would simply not have this container update each time an image is released and treat it like a VM. (Doing updates within the container)

[thelamer]

Docker commit is what Kasm uses https://docs.docker.com/reference/cli/docker/container/commit/
Just saves a running container to a tag, but yeah as @j0nnymoe said what you are asking for is impossible if you want to ingest new containers.