Beiträge von MarcS

    yes many times. also rebooted etc.

    Docker works fine and I have 3 other containers all working well.

    A strange thing happens everytime after rebooting. Docker shows in OMV GUI as up and "running", but the containers are not working until I do a docker restart once. Then magically, all existing containers work well.

    I checked all Google references to "layer doesnt exist" but they all talk about Docker problems really deep inside Docker. I do not believe that I have such a big issue as I run the same configuration on another RPI with Portainer. And also Docker works well, just the installation of Porainer fails. I do think this might have something to do with the OMV scripts.


    New errors when I run this

    Code
      root@rpi42:/usr/share/openmediavault# docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=unless-stopped -v /var/run/docker.sock:/var/run docker.sock -v /srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/myPORTAINER/portainer_data:/data portainer/portainer-ce:latest
    Unable to find image 'docker.sock:latest' locally
    docker: Error response from daemon: pull access denied for docker.sock, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
    See 'docker run --help'.
    root@rpi42:/usr/share/openmediavault#

    yes I am sure this is the only Docker folder and Docker works fine. I have other containers up and running.

    Its just Portainer that des not install

    thanks for all your help!


    Your second command throws an error:

    Code
    root@rpi42:/# docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
    docker: Error response from daemon: layer does not exist.
    See 'docker run --help'.

    Not what is shown on your previous post.

    Your last ls command shows your docker Root inside the merged pool.


    You can see it with this to try to confirm it

    ls -al /srv/dev-disk-by-uuid-*/Docker/

    As I said the Docker sits on an SSD which is part of a merged pool. The Docker path in OMV points directly to the SSD but since that SSD is part of the merged pool, the Docker folder will also show up inside the merged pool.

    I found something in here:


    Code
    "error evaluating symlinks from mount source \"/srv/mergerfs/JGPool190/Docker/volumes/portainer_data/_data\": lstat /srv/mergerfs/JGPool190/Docker/volumes/portainer_data: no such file or directory"

    This is related to an old mergerfs Pool which does not exist any longer. Everything is now on "/srv/mergerfs/Pool2/Docker..."


    Do you know where this is stored?

    Code
    root@rpi42:/srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes# docker ps -a
    CONTAINER ID   IMAGE          COMMAND                  CREATED        STATUS                   PORTS                                   NAMES
    e56590e3be91   2991a96e6ce3   "/init"                  3 hours ago    Exited (0) 3 hours ago                                           nginx-app-1
    e96b3cddf842   1735b64c8e82   "/scripts/run.sh"        3 hours ago    Exited (0) 3 hours ago                                           nginx-db-1
    1209b706b623   1412ed88500c   "/entrypoint.sh apac…"   10 hours ago   Up 2 hours               0.0.0.0:8080->80/tcp, :::8080->80/tcp   nextcloud2-app-1
    1ce345cbf15f   488f98fe1814   "docker-entrypoint.s…"   10 hours ago   Up 2 hours               3306/tcp                                nextcloud2-db-1

    I removed all data and confirm there is no portainer folder.

    then I use OMB GIU to install.

    Error message as follows:

    sure. thanks

    Code
    root@rpi42:/srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes# ls -al /srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes/portainer_data/_data
    
    total 0
    drwxr-xr-x 1 root root  0 Jan 18 18:42 .
    drwx-----x 1 root root 10 Jan 18 18:42 ..
    root@rpi42:/srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes#

    ls -al /srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes/portainer_data

    total 0

    drwx-----x 1 root root 10 Jan 18 18:42 .

    drwx-----x 1 root root 172 Jan 18 19:26 ..

    drwxr-xr-x 1 root root 0 Jan 18 18:42 _data

    root@rpi42:/srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes# ls -al /srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes

    total 32

    drwx-----x 1 root root 162 Jan 18 18:42 .

    drwx--x--- 1 root root 146 Jan 18 18:36 ..

    drwxr-xr-x 1 www-data www-data 420 Jan 17 20:52 Nextcloud_Application

    drwxr-xr-x 1 openmediavault-webgui spi 276 Jan 18 18:36 Nextcloud_Database

    brw------- 1 root root 0, 56 Jan 18 18:36 backingFsBlockDev

    -rw------- 1 root root 32768 Jan 18 18:42 metadata.db

    drwx-----x 1 root root 10 Jan 18 18:42 portainer_data




    root@rpi42:/srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker/volumes# docker ps -a

    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

    e56590e3be91 2991a96e6ce3 "/init" 2 hours ago Exited (0) 2 hours ago nginx-app-1

    e96b3cddf842 1735b64c8e82 "/scripts/run.sh" 2 hours ago Exited (0) 2 hours ago nginx-db-1

    1209b706b623 1412ed88500c "/entrypoint.sh apac…" 9 hours ago Up 49 minutes 0.0.0.0:8080->80/tcp, :::8080->80/tcp nextcloud2-app-1

    1ce345cbf15f 488f98fe1814 "docker-entrypoint.s…" 9 hours ago Up 49 minutes 3306/tcp nextcloud2-db-1

    thanks - tried every step but my problem remains.

    My Docker folder is on an SSD (not the standard path). Could that cause a problem? (Seems illogical because Portainer worked fine up until recently).

    Any other ides I could try?


    Many thanks!

    Hi All,

    I am running OMV6 on RPI4 and all was fine until suddenly Portainer stopped working and I cannot reinstall it.

    What I tried:

    - Poretainer - remove

    - Portainer - remove data

    - Portainer - Install

    - several reboots

    (Docker is running OK though).

    Error message:


    Docker storage :: /srv/dev-disk-by-uuid-14a35ebc-6358-492c-af84-4e920f0c55bc/Docker
    Agent port:: 8000
    Web port:: 9000
    Yacht port:: 8001
    ee:: 0
    image:: portainer/portainer-ce
    Enable TLS:: 0
    arch :: arm64
    option :: portainer
    state :: install
    extras :: 6.1.1
    DNS OK.
    No portainer containers or images to remove.
    Pulling portainer/portainer-ce ...
    Using default tag: latest
    latest: Pulling from portainer/portainer-ce
    Digest: sha256:f7607310051ee21f58f99d7b7f7878a6a49d4850422d88a31f8c61c248bbc3a4
    Status: Image is up to date for portainer/portainer-ce:latest
    docker.io/portainer/portainer-ce:latest
    Starting portainer/portainer-ce ...
    Something went wrong trying to pull and start portainer ...

    END OF LINE


    Close