Comment on Portainer Issues With Docker Update FYI

tophneal@sh.itjust.works ⁨1⁩ ⁨day⁩ ago

• irmadlad@lemmy.world ⁨1⁩ ⁨day⁩ ago

  add 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

  source

  • deleted@lemmy.world ⁨1⁩ ⁨day⁩ ago

    You just need to do the following:

    1. systemctl edit docker.service

    2. Add this part above the line ### Lines below this comment will be discarded:

    [Service] Environment=DOCKER_MIN_API_VERSION=1.24

    3. Save the file and exit

    4. systemctl restart docker

    Credit to johannesMEGABAD github.com/portainer/portainer/issues/12925#issue…

    source

    • irmadlad@lemmy.world ⁨23⁩ ⁨hours⁩ ago

      Awesome. Thanks

      source
  • tophneal@sh.itjust.works ⁨23⁩ ⁨hours⁩ 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.

    source

    • irmadlad@lemmy.world ⁨23⁩ ⁨hours⁩ ago

      Alright! Alright! More ways to skin a cat. Thanks.

      source