Just a question, I have updated Proxmox to Version 8.x and everything working well. I don't like having older container images, so I started updating my LXC containers to Bookworm from Bullseye. Every container I updated seemed to handle the change of the libraries and the staged update as documented on the Debian site except for Pi-Hole.
disable non-system services ie. PiHole and DNScrypt proxy and shut them down.
edit the sources lists to Bookworm
atp update
apt upgrade --without-new-pkgs
apt upgrade
reboot
verify OS and restart services
Well what happens is that my DNScrypt Proxy starts just fine but PiHole gets stuck at the lighttpd start. If I wait like 10 minutes, I can start it manually. Nothing in the logs directs me to any issues.
I then created a new container with Bookworm and did a clean install of Pi-hole just to test and it starts up just fine. I know there isn't any guarantees when updating Linux from Major to Major release just just wondered in anyone else has ever seen this?
Yes agreed, when I was running on Raspberry PI's I would never do a in place major OS update due to issues with packages and configurations that wouldn't be updated appropriately. In the container world I needed to try to see if this would have been improved upon, but I can see the same things that I saw on the Pi. This is the first time I did a major in place upgrade in Proxmox and it was worth the education.