After re-installing portainer all my docker containers are not there

  • After a 2 week vacation with my OMV5 off I turned things back on and for a short time portainer showed everything working. I was having trouble keeping OMV5 running as it was coming up with software error with the red banner across the top. After that portainer would no longer run so eventually I reinstalled it and now all my original containers are missing and I am not sure what to do to get them running again?

  • What is the status for docker:


    systemctl status docker

  • Must have typo'd it twice. Here is the output:


    ● docker.service - Docker Application Container Engine

    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e

    Active: active (running) since Wed 2021-03-10 15:17:55 EST; 1h 10min ago

    Docs: https://docs.docker.com

    Main PID: 1039 (dockerd)

    Tasks: 29

    CGroup: /system.slice/docker.service

    ├─1039 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/contain

    ├─1345 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9

    └─1359 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8


    Mar 10 15:17:46 raspberrypi dockerd[1039]: time="2021-03-10T15:17:46.702064461-0

    Mar 10 15:17:46 raspberrypi dockerd[1039]: time="2021-03-10T15:17:46.704137532-0

    Mar 10 15:17:50 raspberrypi dockerd[1039]: time="2021-03-10T15:17:50.081418427-0

    Mar 10 15:17:50 raspberrypi dockerd[1039]: time="2021-03-10T15:17:50.490298249-0

    Mar 10 15:17:51 raspberrypi dockerd[1039]: time="2021-03-10T15:17:51.058582879-0

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.482769862-0

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.681788321-0

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.692385808-0

    Mar 10 15:17:55 raspberrypi systemd[1]: Started Docker Application Container Eng

    Mar 10 15:17:56 raspberrypi dockerd[1039]: time="2021-03-10T15:17:56.041395181-0

    lines 1-21/21 (END)

    ● docker.service - Docker Application Container Engine

    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)

    Active: active (running) since Wed 2021-03-10 15:17:55 EST; 1h 10min ago

    Docs: https://docs.docker.com

    Main PID: 1039 (dockerd)

    Tasks: 29

    CGroup: /system.slice/docker.service

    ├─1039 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

    ├─1345 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9000 -container-ip

    └─1359 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8000 -container-ip


    Mar 10 15:17:46 raspberrypi dockerd[1039]: time="2021-03-10T15:17:46.702064461-05:00" level=warni

    Mar 10 15:17:46 raspberrypi dockerd[1039]: time="2021-03-10T15:17:46.704137532-05:00" level=info

    Mar 10 15:17:50 raspberrypi dockerd[1039]: time="2021-03-10T15:17:50.081418427-05:00" level=info

    Mar 10 15:17:50 raspberrypi dockerd[1039]: time="2021-03-10T15:17:50.490298249-05:00" level=warni

    Mar 10 15:17:51 raspberrypi dockerd[1039]: time="2021-03-10T15:17:51.058582879-05:00" level=info

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.482769862-05:00" level=info

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.681788321-05:00" level=info

    Mar 10 15:17:55 raspberrypi dockerd[1039]: time="2021-03-10T15:17:55.692385808-05:00" level=info

    Mar 10 15:17:55 raspberrypi systemd[1]: Started Docker Application Container Engine.

    Mar 10 15:17:56 raspberrypi dockerd[1039]: time="2021-03-10T15:17:56.041395181-05:00" level=info

    ~

    ~

    lines 1-21/21 (END)

  • systemctl is Debian, maybe your running other OS


    Or maybe sudo systemctl status docker


    Also try sudo docker ps

  • Yeah, it only show the Portainer running.


    Only time something like that happened to me, the syslogs where showing that the disk (where I have my containers) was remounted read-only (for whatever reason)

    I restarted the docker service and then did a reboot and it fixed itself.


    If you want:

    sudo systemctl restart docker or sudo reboot now


    And then check if the containers are there (on the Gui of Portainer) or with docker ps

  • I also just reset permissions on my container folder. That allowed me so see the folder(windows machine running OMV GUI) where before it was saying I did not have permission.

  • If you have access to OMV Gui, you should also have access to Portainer GUI

    IPof PI:9000


    But before, on the OMV Gui, check the "syslogs" and see if any errors are showing there.

    Also there are other logs "bootup, etc" that might give a clue of what is going on.

  • I reinstalled it and now all my original containers are missing and I am not sure what to do to get them running again?

    Set them up again using your existing config folders.


    This process is especially easy, if you have used docker-compose files which you can run as stack in portainer

  • I'm not sure how to do that. One of my setups was nextcloud that I got significant help on from KM201. I really don't want to mess that up. Do you just put the .json file in the stack web editor? There is more than one .json file in the containers.

  • There is more than one .json file in the containers.

    What do you mean with that?


    It is difficult for me to understand in which status your system is.

    Did you reinstall completely or just Portainer? If you reinstalled Portainer, how did you do that?

  • I updated all the updates in OMV 5 and then went to OMV-extras/Docker and installed portainer from there. I was not able to start portainer at that point using the open portainer button.

  • I don't see how that would help. OMV5 is running fine and portainer is running fine it just isn't seeing the previous created containers.

  • No I did not do a fresh install of OMV5 although I think one of the updates was OMV5. I think I found the nextcloud yaml file in the following path \\RASPBERRYPI\Containers\volumes\portainer_data\_data\compose\2.

  • Then you can check if the bind mounts from that yaml file are still there (should be). Then you can just deploy the stack using that file. Should work.

    To be on safe side, make a backup.


    What is strange: if the files are still there, why do they not show up in portainer?


    When you reinstalled portainer, did you map the /data folder in the container to \\RASPBERRYPI\Containers\volumes\portainer_data on the host?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!