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

Managing Mac’s compared to PCs is such a dream it’s soooooo easy

It should be absolutely possible to put a data SSD in, that model also has an unofficial max ram capacity of 6gb

DEI is a discriminatory policy for a repo? Granted I’m no programmer, but that feels like a made up “problem” to be solving for something like X.org. The README looks like the ravings of a spurned ex employee or someone that may need some professional help.

lol I usually just try my luck with yay’s “build anyway?”