The idea in four steps

  1. Check that the app works before you touch it. Never patch something that is already failing.
  2. Take a snapshot so there is a way back.
  3. Run the updates.
  4. Check again. If the app still answers, keep going. If it does not, roll back to the snapshot.
  1. Checkthe app works now
  2. Snapshotpct snapshot
  3. Patchapt-get upgrade
  4. Check againsame health check
  5. Works: keep the snapshotdelete it after a few daysBroken: roll backpct rollback, then start
Check, snapshot, patch, check again. The second check decides whether you keep going or roll back.

What you need

Step by step

1. Check it works now.

curl -fsS https://app.example.com/health

2. Take a snapshot and wait for it to finish:

pct snapshot 105 pre-patch --description "before apt upgrade"

3. Run the updates inside the container:

pct exec 105 -- bash -c 'apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y upgrade'

4. Check again, giving services a few seconds to restart:

sleep 30
curl -fsS https://app.example.com/health

5a. It works. Keep the snapshot for a few days as a rollback point, then delete it:

pct delsnapshot 105 pre-patch

5b. It does not. Stop the container, roll back, and start it again:

pct stop 105
pct rollback 105 pre-patch
pct start 105

Limits you should know about

Making it a monthly habit

The manual version is easy to skip. Pontavia's Proxmox Safe Patch ($59) is an n8n workflow that does exactly this. It checks your app answers, takes a snapshot, runs apt upgrade inside the guest, then checks again. If the app still works, the snapshot stays as a rollback point and older ones are cleaned up. If it broke, the guest is rolled back, started again, and you get an alert saying what failed.

It starts in report-only (dry run) mode, never patches a guest that is already failing a check, and never installs without a finished snapshot. It only deletes snapshots it made itself, and reboots only if you allow it. It was tested on Debian 12 and Ubuntu 24.04 containers, including a reboot. Virtual machines use the same steps but are not tested yet.

Frequently asked questions

Can I take a snapshot of a running Proxmox container?

Yes, on storage that supports snapshots. pct snapshot works on a running container. If your storage does not support snapshots, take a vzdump backup before patching instead.

What if my storage does not support snapshots?

Then pct snapshot will fail. Take a vzdump backup before patching and restore it if the update breaks something. It is slower but gives you the same safety net.

Should I use apt-get upgrade or dist-upgrade?

For routine patching, apt-get upgrade is the conservative choice because it does not remove packages or add new ones. dist-upgrade can change the package set and is better kept for planned upgrades.

Is this how I should patch the Proxmox host itself?

No. Host updates and reboots are a separate procedure. See the guide on finding Proxmox nodes that need updates or a reboot.

Questions about your own setup? Send a message or book a free 15-minute call.