I ran into the same issue over the weekend. The end-goal for my Proxmox setup is basically the same deployment you have. It's good to see the issue was addressed quickly by the community.

> Running docker inside LXC is weird.

Knowing when to use a vm and when to use a container is sometimes an opaque problem.

This is one of those cases where a VM is a much better choice.

> As an aside... Because one node didn't start, and my Proxmox cluster has only two nodes, it can't reach quorum, meaning I can't really make any changes to my other node, and I can't start any containers that are stopped. I've recently added another Zigbee dongle, that supports Thread, and it happens to share same VID:PID combo as the old dongle, so due to how these were mapped into guest OS, all my light switches stopped working. I had to fix the issue fast.

Lesson in here somewhere. Something about about a toaster representing the local intelligence maxima?