Portainer failures

[binsaif]

"I have persistent docker.sock permission/connection failures inside a Debian 13.2 VM running on Proxmox VE (latest QEMU updates). The Docker service runs, but Portainer cannot connect to it (fails when clicking 'local'). All standard fixes (GID, privileged, API checks) have failed. Is this a known Kernel Security Context (AppArmor/SELinux) conflict specific to Debian 13/Bookworm guests on Proxmox that requires a non-standard VM configuration tweak, or is this environment fundamentally incompatible with the default Docker socket connection?"

 

[6equj5]

Docker 29? Portainer is not yet ready, needs workaround.

 

[binsaif]

Has anyone else confirmed that Docker CE v29.x is fundamentally incompatible with the Proxmox/Debian Host Kernel's security context when accessing the socket, requiring a rollback to v28.x for stable operation?

 

[6equj5]

It's not a problem of Docker or Proxmox/Debian. It's a problem of Portainer using deprecated API. Net is full about it.

https://github.com/portainer/portainer/issues/12925

 

[Ernst T.]

The developers of Portainer apparently can't get the container to work with Docker 29.x. Or maybe they don't want to...

Take a look there: https://github.com/portainer/portainer/issues/12925

 

[binsaif]

I will continue to operate using Docker CE v28.x until a proper fix or official support for the newer version is released by Portainer. Thank you all for your contributions and attempts to help.