Hi,
Usual updates, containers.io gets updated from 1.x to 2.x.
Connecting to portainer, all things look (but only once) fine
Clicking anywhere makes the environment go down
I've just delete/recreate portainer, and reinstall Docker, without any success.
Any ideas ?
One more with problems here after updates. Reinstalled portainer didn't solve.
There is an issue on Github: https://github.com/portainer/portainer/issues/12925 Portainer uses Docker API 1.41 but the minimum for Docker 29.0 is 1.44. So a possible solution is a downgrade to the previous docker or use the OMV compose functions......
Another solution from here: https://gathering.tweakers.net…message/83909852#83909852
systemctl edit docker.service
Add this part above the line ### Lines below this comment will be discarded:
[Service]
Environment=DOCKER_MIN_API_VERSION=1.24
Save the file and exit
systemctl restart dockerHowever, I cannot find a Docker config file in OMV....
Works
However, I cannot find a Docker config file in OMV....
What do you mean? The compose plugin doesn't config docker other than writing the docker path in /etc/docker/daemon.json. Changing the min api version shouldn't be needed. This is only a portainer problem which I assume they will update soon. Just another reason to use the compose plugin instead of portainer.
Solved.
Thank you DjoeC.
What do you mean? The compose plugin doesn't config docker other than writing the docker path in /etc/docker/daemon.json. Changing the min api version shouldn't be needed. This is only a portainer problem which I assume they will update soon. Just another reason to use the compose plugin instead of portainer.
There are many more reports about other containers with the same problem.... Yes, it is a container problem - however the docker release notes specify version 29.0.0-rc.3 as latest version. It is questionable that the OMV update would recommend installing an RC version over latest stable in the available updates.
So, even though you are correct and a minimum version should not be necessary it's nice that it's possible. Now, if I can only find the correct docker.service file location to put it in....
And, NO - that is NOT what I want and YES the OMV compose plugin is what I mainly use with its limitations (i.e. see open issue about maximum lines per screen). We've had a conversation about Compose as replacement for Portainer and others b4, the conclusion was that OMV offers a lot of functionality but is not a replacement - and that's not a problem, it does not detract from the OMV (and extras) other benefits. Same way as Portainer has (for me!) certain benefits over/in addition to OMV.
Today's OMV Docker updates also triggers a failure with Watchtower refusing to run is you are using the containrrr/watchtower image. A solution for this is to switch to the nickfedor/watchtower image.
There are many more reports about other containers with the same problem.... Yes, it is a container problem - however the docker release notes specify version 29.0.0-rc.3 as latest version. It is questionable that the OMV update would recommend installing an RC version over latest stable in the available updates.
omv-extras adds the stable bookworm docker repo. You will only get an RC if Docker puts an RC in their stable repo (don't think they do that). I don't see rc3 on my systems. The only containers that should have a problem with this are containers managing other containers or interacting with docker service itself.
apt-cache policy docker-ce
docker-ce:
Installed: 5:29.0.0-1~debian.12~bookworm
Candidate: 5:29.0.0-1~debian.12~bookworm
Version table:
*** 5:29.0.0-1~debian.12~bookworm 500
500 https://download.docker.com/linux/debian bookworm/stable amd64 PackagesYou don't need to edit a file. sudo systemctl edit docker.service
No need to start using all caps on me because I suggest using the compose plugin instead of portainer. I spend a lot of time on the compose plugin and get tired of portainer problems. I think I am entitled to say it once in a while. My comment wasn't directed solely at you. Just people having portainer problems in general.
The max lines per screen is not something I will change because it forces the number of lines on every user. Using the filter is what I use and my dev box has way more containers than any sane user should. Someone should contribute code to core OMV to add a user selectable number of rows on the datatable component.
A solution for this is to switch to the nickfedor/watchtower image.
Or use the compose plugin's update. I know that is the hated route though.
No need to start using all caps on me because I suggest using the compose plugin instead of portainer. I spend a lot of time on the compose plugin and get tired of portainer problems. I think I am entitled to say it once in a while. My comment wasn't directed solely at you. Just people having portainer problems in general.
Apologies.... I was certainly not personal to you or anyone. I appreciate the work and the resulting product (can't wait for V8 
)
Portainer is certainly not perfect and development of the ce version appears to lag behind, but it has a place in my workflow. When V8 appears I'll be setting everything up from scratch again and look at the then available best options. Will probably be installing extra containers as well Not sure what the cutoff number for "sane" is though.
Not sure what the cutoff number for "sane" is though.
I have 125 files in my dev environment. Some of those are multi container. That is an extreme number of containers on one system in my opinion.
Or use the compose plugin's update. I know that is the hated route though.
I took your suggestion and reverted to the containrrr/watchtower. However, after a very long compose plugin update, watchtower began to throw the same error again and mail bombed with with the error, once for each container I run:
Error response from daemon: client version 1.25 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer versionMaybe you are saying I don't need to run Watchtower is I use the compose plugin update function?
Maybe you are saying I don't need to run Watchtower is I use the compose plugin update function?
That is what I am saying. I don't use watchtower. So, I don't know when they will update their container to work with the "new" docker api.
That is what I am saying. I don't use watchtower. So, I don't know when they will update their container to work with the "new" docker api.
There are at least three Watchtower images that I know of. The one that suddenly started to fail, containrrr/watchtower, hasn't been updated in some number of years. The nickfedor/watchtower image was "touched" as recently as a few hours ago.
Another solution from here: https://gathering.tweakers.net…message/83909852#83909852
Codesystemctl edit docker.service Add this part above the line ### Lines below this comment will be discarded: [Service] Environment=DOCKER_MIN_API_VERSION=1.24 Save the file and exit systemctl restart docker
Works for Portainer only or all other containers that use the API ? I use socket on Portainer, docker-socket-proxy, watchtower and cAdvisor.
No need to start using all caps on me because I suggest using the compose plugin instead of portainer. I spend a lot of time on the compose plugin and get tired of portainer problems. I think I am entitled to say it once in a while. My comment wasn't directed solely at you. Just people having portainer problems in general.
Apologies ryecoaaron, I'm not pointing at any of the two solutions and in no way at you, both have pros and cons, and in fact I'm using a mix of both (which maybe the worst ideas whatsoever )
The nickfedor/watchtower is completely up to date:
time=2025-11-11T10:39:37Z level=info msg=Note that the first check will be performed in 112 hours, 20 minutes, 22 seconds
time=2025-11-11T10:45:39Z level=info msg=Watchtower 1.12.1 using Docker API v1.51Works
grep output is blank for me, and the fix doesn't work.
systemctl edit docker.service gives me /etc/systemd/system/docker.service.d/.#override.confXXXXXXXXXX
Don’t have an account yet? Register yourself now and be a part of our community!
