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.
Dang. I see what you mean, lots of videos of the screensaver but not many gifs with the sweet spot of a corner. But I did find one that immediately puts out the goods
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.