Beiträge von vandoe

yes I restarted docker rebooted the Pi. Still no change.

Did it again for good measure. Still not working.

I did the containers folder as well.

Zitat von KM0201

Owner should be root r/w (not admin)

Groups should be users r/w

Guests: None

I'm not following. Under shared folders I have a tab reset permissions. this is what it looks like.

Just went backward, because portainer stopped working so I removed and reinstalled it and I'm back to portainer does not see any of the containers.

I do have reset perms installed and have tried a couple of times to reset using the option adim read/write users read/write. Don't think it helped. Portainer is now failing to open so I can't tell

Zitat

Are you doing that command as root or using sudo?

yes I'm SSH as root

I just tried to start one of my containers from the command line by listing the containers, finding the ID and using command docker start and I got the same error

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

Error: failed to start containers: 54573beea72e

Zitat

I remember helping him now (had to go through my PM's).... His containers folder was absolutely right when I helped him, so the reality is, it's either under /srv, or... it's been deleted somehow (the permission error that the containers are throwing is interesting.. but we can figure that out later.

Everything seems to be just how you left it. As far as I can tell everything is in the right place.

Containers are in this directory:

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

config files are in this directory:

/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config

Here is a screen shot of the the containers all stopped.

Here is the result of cd /srv

root@raspberrypi:~# cd /srv
root@raspberrypi:/srv# ls
dev-disk-by-label-Files
dev-disk-by-uuid-12E426FAE426E029
dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f  "this is the drive where all the containers are located"
dev-disk-by-uuid-5da720d0-d768-47fe-98c0-09f479a6838e
dev-disk-by-uuid-DC84F32C84F307B2
ftp
pillar
salt

I know where the containers are and I know where the configuration files are. All the containers are showing up now in portainer I just can't get them to start.

Here is where my docker containers are:

root@raspberrypi:/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Containers# ls -al
total 60
drwx--x--x 13 root users  4096 Mar 11 15:48 .
drwxr-xr-x  6 root root   4096 Mar 10 15:43 ..
drwxrwsr-x  4 root users  4096 Feb 13 12:26 buildkit
drwx-----x 11 root root   4096 Mar 11 15:53 containers
drwxrwsr-x  3 root users  4096 Feb 13 12:26 image
drwxrwsr-x  3 root users  4096 Feb 13 12:26 network
drwx-----x 96 root root  12288 Mar 11 15:53 overlay2
drwxrwsr-x  4 root users  4096 Feb 13 12:26 plugins
drwx------  2 root root   4096 Mar 11 15:48 runtimes
drwxrwsr-x  2 root users  4096 Feb 13 12:26 swarm
drwx------  2 root root   4096 Mar 11 15:49 tmp
drwxrwsr-x  2 root users  4096 Feb 13 12:26 trust
drwx-----x  9 root root   4096 Mar 11 15:48 volumes

and the config files:

root@raspberrypi:/srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config# ls -al
total 24
drwxrwsr-x  6 root users 4096 Feb 13 15:55 .
drwxr-xr-x  6 root root  4096 Mar 10 15:43 ..
drwxrwsr-x  7 root users 4096 Feb 13 16:41 cache
drwxrwsr-x  9 root users 4096 Feb 13 15:25 nextcloud
drwxrwsr-x  4 root users 4096 Feb 13 15:19 nextclouddb
drwxrwsr-x 12 root users 4096 Feb 13 15:19 swag

Seems like this looks OK

I tried refreshing no go and I logged out closed the tab and opened portainer from OMV same result they all share the same error message.

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

I did the control f5 and reloaded the page. I'm pretty sure it is not a cached page. The drive that holds the container's was off for two weeks

Here's the output from 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-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Containers

WARNING: No memory limit support

WARNING: No swap limit support

WARNING: No kernel memory TCP limit support

WARNING: No oom kill disable support

WARNING: No blkio throttle.read_bps_device support

WARNING: No blkio throttle.write_bps_device support

WARNING: No blkio throttle.read_iops_device support

WARNING: No blkio throttle.write_iops_device support

This is what I get when I go to the portainer container. I don't see the volume section even after scrolling all the way down

Here is a screen shot of my dashboard page. I can't find an equivalent page to the one you posted.

On my portainer dashboard page there is an endpoint defined as shown below. Could it be that I need to re-point portainer because the docker path in OMV-extras is correct.

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

I didn't map anything. I just installed portainer by clicking install from the OMV5 console..

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.

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.