Comment on Portainer Issues With Docker Update FYI
irmadlad@lemmy.world 4 months agoadd an override for the docker.service file
Can you elaborate? I made the post hoping to save someone a couple hours banging their head on the keyboard like I did. LOL
So something like :
sudo nano /usr/lib/systemd/system/docker.service
What was the format of your entry to specify min api version 1.24? I’m curious and always down to learn new tricks.
'presh
You just need to do the following:
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 docker
Credit to johannesMEGABAD github.com/portainer/portainer/issues/12925#issue…
Awesome. Thanks
tophneal@sh.itjust.works 4 months ago
Here’s the method I used from one of the issues on GitHub github.com/portainer/portainer/issues/12925#issue…
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.
irmadlad@lemmy.world 4 months ago
Alright! Alright! More ways to skin a cat. Thanks.