just some guy

Here’s the method I used from one of the issues on GitHub https://github.com/portainer/portainer/issues/12925#issuecomment-3516549977

Iirc my docker.socket wouldn’t let me just stop docker.service to edit it as described in the post, so I made /etc/systemd/system/docker.service.d/override.conf with the 2 required lines. After saving it and running daemon-reload I was able to access my containers in portainer again.

You can also add an override for the docker.service file to specify min api version 1.24. Had to do that last night