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

What is your docker storage path in omv-extras >> docker?

By default the docker storage path is /var/lib/docker

if you use the default, than the yaml files are in

/var/lib/docker/volumes/portainer_data/_data/compose

you mentioned another path in one of the posts above

\\RASPBERRYPI\Containers\volumes\portainer_data\_data\compose\2.

so I am wondering if you changed the docker storage path in your previous setup and now it is maybe back to default

So basically you would have to set the docker storage path back to the storage path you previously used and everything should be up and running again.

Do you have the same on your system (where the arrows are pointing)?

Can you post a screenshot of the complete dashboard?

Zitat von vandoe

I can't find an equivalent page to the one you posted.

In Portainer >> Containers >> Portainer

scroll a bit down.

The link does not work for me.

The screenshot looks definitely wrong.

First try if clearing browser cache changes anything.

If not I would make a backup of

/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Containers/volumes/portainer_data

then remove portainer and reinstall it. Both from omv-extras.

The volume should not be removed during removal, but I would prefere to have a backup.

Zitat von macom

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?

Alles anzeigen

Even if he didn't... as soon as he logged in to a new portainer session.. it would show his old containers, would it not? Yes, Portainer would not have any custom settings, but if the docker service is properly pointing at his containers folder, as soon as he installs Portainer and logs in, it should have all his containers there (or that is how it has been for me in the past).

Either someone has messed w/ that drive while he was gone and he doesn't know it, or somehow docker is looking in the wrong directory despite what the webUI says. OP, you mentioned a reinstall.. have you cleared your browser cache and then looked at the docker tab (Hold Cntrl click F5 while on the OMV webUI)? You could be seeing a cached setting..

I gotta bolt in a minute, but I'm curious what the the command line shows vs the webUI...

OP, what is the output of:

docker info | grep Docker

That should give you an output something like this and show the root directory docker is looking in (line 4)

ken@openmediavault:~$ docker info | grep Docker
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
 Docker Root Dir: /srv/dev-disk-by-label-D1/Containers
ken@openmediavault:~$ 

Gotta run, but initially I'm out of ideas on this, unless somehow your drive is mounted under a new path.

Zitat von Soma

AFAIK, Portainer is just a container in docker that sees which containers are running in docker.

You can do all in compose and portainer will still sees them.

What seems more likely is that his root folder for docker is somewhat changed.

vandoe

Can you see on the OMV Gui what is the root for docker? It will look something like this (that is my path, yours will look/be different):

Then, maybe you can search the file system to find where your folders are and see if it matches:

In my case above ----^^^^

Code

~$ sudo ls -al /srv/dev-disk-by-label-DATA/Docker/
total 60
drwx--x--x 13 root root  4096 Mar  9 08:09 .
drwxr-xr-x 10 root root  4096 Feb 25 22:17 ..
drwx--x--x  4 root root  4096 Feb  1 19:14 buildkit
drwx-----x  8 root root  4096 Mar  3 20:21 containers
drwx------  3 root root  4096 Feb  1 19:14 image
drwxr-x---  3 root root  4096 Feb  1 19:14 network
drwx-----x 62 root root 12288 Mar  9 08:09 overlay2
drwx------  4 root root  4096 Feb  1 19:14 plugins
drwx------  2 root root  4096 Mar  9 08:09 runtimes
drwx------  2 root root  4096 Feb  1 19:14 swarm
drwx------  2 root root  4096 Mar  9 08:09 tmp
drwx------  2 root root  4096 Feb  1 19:14 trust
drwx-----x  4 root root  4096 Mar  9 08:09 volumes

Alles anzeigen

And then, my configs are on "appdata":

Code

~$ sudo ls -al /srv/dev-disk-by-label-DATA/appdata/
total 44
drwxrwsrwx  8 root                  users 4096 Feb 21 00:22 .
drwxr-xr-x 10 root                  root  4096 Feb 25 22:17 ..
-rw-r--r--  1 pi                    users 2519 Feb 20 18:54 docker-compose.yml
drwxr-sr-x  4 pi                    users 4096 Feb 20 19:32 mariadb
drwxr-sr-x  5 root                  root  4096 Feb 21 00:22 mariadb_10.5
drwxr-sr-x  2 root                  root  4096 Jan  7 15:58 motioneye
-rw-r--r--  1 pi                    users 1547 Feb 18 12:43 motioneye.subdomain.conf.sample
drwxr-sr-x  4 root                  root  4096 Feb  2 16:12 nextcloud
-rw-r--r--  1 pi                    users   20 Feb 16 22:21 phpinfo.php
drwxr-sr-x  2 openmediavault-webgui root  4096 Mar 11 20:19 redis
drwxr-sr-x 12 pi                    users 4096 Feb  1 21:49 swag

Alles anzeigen

See what you have and try to remember how it was before.

If it looks right to you, reinstall docker and reboot.

If you see that the root folder has changed, say something and we can go from there.

Alles anzeigen

That is the only logical conclusion I can come up with.

Zitat von vandoe

I just finished uninstalling and reinstalling portainer and now it is seeing all the original containers but they are all stopped. After trying to start them I am getting a bunch of errors. For example here is the error when trying to start Nextcloud:

Failure

OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/init": permission denied: unknown

Try refreshing your browser cache for Portainer (Contrl + F5 while in Portainer)