Comment 18 for bug 1977919

This happened to two of our instances in AWS. In the hope that this is helpful to anyone: in an attempt to avoid having to mount the root volumes on another instances, we disabled docker and containerd in the small timeframe between SSH becoming accessible and the kernel panic, by running something like this from a laptop:

while true; do
  ssh <instance> "sudo systemctl disable docker.service; sudo systemctl disable containerd.service"
done

This allowed us to revert to the previous kernel without having to mount the root volume on a different instance.