Docker 29 is currently not compatible with Portainer. If you upgrade, you may experience issues.

[Nick-Portainer]

Docker 29 is currently not compatible with Portainer. If you upgrade, you may experience issues. Our team is already working on support for Docker 29 and we will provide an update once it is fully validated.

[Nick-Portainer]

The recently released Docker Engine 29.0.0 contains breaking changes that are not compatible with the current supported versions of Portainer - 2.33-LTS and the latest STS. This specifically affects Docker Standalone environments running on the new Docker Engine 29.0.0. Connection attempts to these environments will likely fail.
For optimal stability, we continue to recommend running Docker versions listed on our official requirements page: https://docs.portainer.io/start/requirements-and-prerequisites
Workaround
Our community was quick to identify a temporary workaround that restores connectivity by specifying the minimum Docker API version the daemon should use.
You can find the details and steps for this workaround in the following GitHub comment:
➡️ Workaround Instructions on GitHub Issue #12925
We are actively working on changes to fully support Docker Engine 29.0.0 and its required API version.
Thank you for your patience and for being an engaged part of the Portainer community!

[ptr727]

Let me fix the title: "Portainer is currently not compatible with Docker 29"

[LittleNewton]

I witnessed the same issue. Waitting for the upgrading of portainer!

[RLSinRFV]

Thanks for the update @Nick-Portainer

[DouradoCtrl]

Thanks @Nick-Portainer, I even reinstalled my Fedora because I thought the problem was in version 43, which was recently updated. A series of coincidences.

[johannesMEGABAD]

Hey! Glad this issue is on being worked :) Also glad the workaround can help meanwhile ^^

[riemerSTOS]

Thanks @Nick-Portainer for the information!

[gperuchon]

Thanks for the update

[itaiber2000]

i tried go back to 2.20 as managed in the workaround but then all of the stacks become limited and couldn't edit them inside portainer.
im waiting for the fix for docker 29.

[MichaelSchmidle]

Connecting to Docker 29.0.0 via Portainer Agent interestingly fully works, though. So I use the Portainer Agent to connect to the local environment of Portainer itself, too.

[tgmct]

I've been bit by this also. There are a few things to discuss. The notion that Portainer is throwing a Podman related error when it's not even installed is obviously a Portainer issue, not Docker's. I suspect that a parent and child pointing session is developing... But who is the parent and who is the child?

[RLSinRFV]

@Nick-Portainer, any update on timing for this Docker29 compatibility with Portainer update?

[Nick-Portainer]

This is scheduled for our next STS release which will be coming out within our normal patch cycle this month. Once I have a confirmed date I will share it here

[Smokex365]

Would it be worth suggesting to add a "stable" tag in addition to the version and latest tags? A tag that we can be reasonably sure is stable and can be independently rolled back to previous versions in instances like this. I know it probably wouldn't have prevented this particular issue since it was docker side but it might be useful in general.

: for those on specific versions
:stable for latest known working version
:latest for well, latest

[topa-LE]

Thanks!

[vdrover]

following

[cruix89]

i started my server today... bad luck

[ArmyaAli]

Yeah same, I just installed portainer on my homelab for the first time lol

[SamuelGaona]

Try this

https://github.com/orgs/portainer/discussions/12926#discussioncomment-14960044

[cruix89]

guys i'm searching for a alternative for this problem and found this project:

https://getarcane.app/

i tested it and honestily i thinked better than portainer... arcane have a system prune shortcut and automatic containers/compose updates
working perfectily with docker 29+

[dojoca]

This looks really nice, it's a shame their web site doesn't have a single screenshot though.

Edit: just saw screenshots on their github. Looks really good, the looooong delay with portainer fixing this issue is definitely pushing me to give other options like this (or Komodo) a try.

[dojoca]

Any updates on when this update will get pushed out to LTS business users?

[tgmct]

Any updates on when this update will get pushed out to LTS business users?

I would think that being a Business Edition user would give you some priority. I would certainly submit a support ticket to get it sorted out; particularly where the CE has had a workaround solution available for a couple of weeks.

[AndyXheli]

I did the same workaround on my Business Edition and it worked