Incus Snapshots
They save the day!
If you're running Inductive Automation Ignition in Linux (and imo you should be), and you're running it in containers (and imo you should be), while you're probably using Docker (love that), I'd also strongly recommend nesting that Docker environment in an Incus (LXC) container.
Container perks with VM-like snapshot capabilities and better isolation—it's ideal for stateful applications like Ignition.
Case in point: I risked upgrading a production server from Ignition 8.1.48 to 8.3.3 this morning, even though I had to be at my son's school performance early afternoon. Not ideal timing, right? But I was confident because I knew I could simply:
incus snapshot create docker1
Then when the newly upgraded 8.3.3 container started crashing repeatedly on a vague JVM fault, I just ran:
incus snapshot restore docker1 snap0
Back up and running within 30 seconds. Made it to the performance with time to spare. Now I can investigate the 8.3.3 issue later without pressure. Incus FTW! 👏🏻