HA stuck in "Started containerd container - Stopped containerd container loop" after HAOS 11 update atemped

[diegoantilles]

Describe the issue you are experiencing

Home Assistant is stuck in a loop trying to start the "containerd container".

This happens for several minutes, then the hole VM reboots, and the issue begins form start again

The instance is a VM running on a Proxmox virtualization server.
All the HAOS updates on this VM before worked flawless.

What operating system image do you use?

ova (for Virtual Machines)

What version of Home Assistant Operating System is installed?

10.5

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1.Press install HAOS 11 Option in the settings menu
2.
3.
...

Anything in the Supervisor logs that might be useful for us?

-

Anything in the Host logs that might be useful for us?

-

System information

No response

Additional information

No response

[agners]

After three startups the GRUB bootloader should select the other boot slot. If that is not the case, you can do that manually using arrow keys. Does choosing the other boot slot helps to resolve the issue?

[diegoantilles]

After three startups the GRUB bootloader should select the other boot slot. If that is not the case, you can do that manually using arrow keys. Does choosing the other boot slot helps to resolve the issue?

After a few failed attempts to start the containerd contaiers and several forceful restarts via Proxmox, HA starts again and is running, but still on HAOS 10.5 with the notification to upgrade to HAOS 11. From there on, if I try updating, the issue stays the same.

[hocomadvies]

I experience more or less the same issue. Also on Proxmox VM when push upgrade to 11 the spinning wheels stays for ever and nothing seems to happen. After reboot after long wait it still says there is an udate for HOAS. What would be the Cli command for running the update? Might try that see if that make a differences.

[diegoantilles]

Unfortunately the problem still persists on my Proxmox instance and I'm stuck on OS 10.5 so far. Does any of you have an idea what could be causing the problem?

[github-actions]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[diegoantilles]

Still persists on my Proxmox instance and I'm still stuck on OS 10.5 so far... don't know how we will get rid of the issue.

[github-actions]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.