Recent content by diviaki

OK I see. So when snapshotting a running container only the filesystem is snapshotted. As process state is not stored for snapshots, restoring snapshots that were taken on running containers involves the risks of loosing any unwritten internal caches of a program. Going back my opening question...

Thanks Dominik. Do you know what happens in edge cases where an application could not write all it's state to disk?

Thanks for pointing to AbstractConfig.pm - yes, I now see the container freezed, mount points synced, finally the container unfreezes. I still could not find where is the frozen process state saved to disk, not the code nor such files.

I find it strange that vmbr0's and enp0s's address are the same with ports not bridged. Also make sure to read this when bridging the host ethernet interface at Hetzner: https://docs.hetzner.com/robot/dedicated-server/network/net-config-debian/#bridged

Hi! First thanks for the Proxmox suite, it just works, and makes my poor-mans-sysadmin role a lot easier. There's one thing I'd like to better understand about snapshotting containers. Do I need to pct stop - snapshot - start my containers to have reliable snapshots? I'm not into python but...