Posts by Copaxy

    ls -al /var/lib/docker/volumes


    Maybe it helps. My syslog shows something is down


    Sorry but this is really weird, :rolleyes:


    Since you run as root, no need for sudo.

    docker ps -a | grep -i portainer

    I know..that is why i am here. Just randomly after updating portainer over the extras to the latest version it started to become unstable after one day and now it totally refuses to work.

    I have no clue anymore what the error might be. Before it was totally fine, no issue.


    Code
    root@meinnas:~# docker ps -a | grep -i portainer
    d681f9ca4876   portainer/portainer-ce                          "/portainer"             45 seconds ago   Created                     0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp, 9443/tcp   portainer
    root@meinnas:~#

    After the installation it fails and the container is just created

    Code
    root@meinnas:~# sudo docker stop portainer
    portainer
    root@meinnas:~# sudo docker rm portainer
    portainer
    root@meinnas:~# sudo docker ps -a | grep -i portainer
    root@meinnas:~#


    It seems gone now


    Reinstall still fails


    The output of

    sudo docker ps -a


    It completely fails to install



    I tried to reinstall portainer over the gui in extras.


    Yes, but from what I'm seeing from Copaxy , I'm thinking he had Portainer running, NOT by OMV-Extras but maybe by docker-compose.

    And all the instructions I'm giving are based on a Portainer installation via Extras.

    I only used the extras tool, i didn't manually create a portainer container

    Please, outputs of:


    sudo ls -al /var/lib/docker/volumes/

    sudo ls -al /var/lib/docker/volumes/portainer_data


    And what command you used to make the copy of the folder?


    Code
    root@meinnas:~# sudo ls -al /var/lib/docker/volumes/portainer_data
    ls: cannot access '/var/lib/docker/volumes/portainer_data': No such file or directory


    The command i used to make a copy was:


    Code
    sudo cp -a  /var/lib/docker/volumes/portainer_data /var/lib/config/portainer_data-backup

    Note: The config folder is just the folder i keep other containers container data -> The name of config is maybe a bit missleading

    docker ps -a


    Code
    root@meinnas:~# docker ps -a
    CONTAINER ID   IMAGE                                           COMMAND                  CREATED          STATUS                      PORTS                                                                                            NAMES
    7176964d2ab1   portainer/portainer-ce                          "/portainer"             17 minutes ago   Created                     0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp, 9443/tcp   portainer
    2df359cfd18e   ghcr.io/benphelps/homepage:latest               "docker-entrypoint.s…"   6 weeks ago      Exited (0) 6 weeks ago                                                                                                       homepage
    ffa32266cfb9   e251b53f1bb7                                    "/bin/sh -c 'apt-get…"   6 weeks ago      Exited (100) 6 weeks ago                                                                                                     keen_bell
    33c23a74804d   gitea/gitea:latest                              "/usr/bin/entrypoint…"   6 weeks ago      Up 5 minutes                0.0.0.0:2234->22/tcp, :::2234->22/tcp, 0.0.0.0:3010->3000/tcp, :::3010->3000/tcp                 gitea
    e90dfc309588   yobasystems/alpine-mariadb:latest               "/scripts/run.sh"        6 weeks ago      Up 5 minutes                3306/tcp
    Code
    root@meinnas:~# docker start portainer
    Error response from daemon: error evaluating symlinks from mount source "/var/lib/docker/volumes/portainer_data/_data": lstat /var/lib/docker/volumes/portainer_data/_data: no such file or directory
    Error: failed to start containers: portainer

    What did you do in a step-by-step?

    On GUI: you clicked "remove" and after " remove data"?

    You checked that the ls -al command still showed portainer_data in there?

    You made a copy of the folder to somewhere else?

    Sorry,


    1. i did remove portainer

    2. i made a copy of the portainer_data folder at another location

    3. i tried to delete the portainer_data with the gui "remove data"

    4. manually by hand deltet the remainings of the portainer_data folder

    checked -> the folder was successfully deleted

    5. reinstall portainer over gui

    That would be the only disadvantage... you cannot set the data volume for portainer if you use the plugin (or at least you couldn't when I tried it.. I usually just install via docker-compose for this reason.


    That said, as long as your containers folder never gets nuked, it wouldn't be an issue.. as that is where portainer (the plugin) stores it's data. So I guess it's all about how your set up is.

    Thanks a lot for the explanation :)


    The only thing is portainer won't start anymore. Doesn't matter if i reinstall it, the container is just created and manual start fails because it can not create the folder. But the boot drive should not have any permission issues, so what is going on

    I think not, you are only deleting Portainer which is a container like any other.


    But if you created stacks via Portainer, then I don't know what will happen.


    If you did created stacks on Portainer, it's time to move to openmediavault-compose plugin.

    You should make a backup of the folder, just in case:

    Oh wow i didn't know that plugin before. This will be much easier if portainer has problems to keep the compose suff from stacks in OMV.

    Is there any backdraw on that plugin or does it work just like portainer?


    I have copied my portainer_data folder as a backup but now portainer won't start. After the installation it says it is created but not started.


    When i try to manually start the container it says portainer could not create the portainer_data folder

    Output of

    docker info | grep -i "Docker Root Dir"

    Code
    root@meinnas:~# docker info | grep -i "Docker Root Dir"
    
    WARNING: No memory limit support
    
    WARNING: No swap limit support
    
    Docker Root Dir: /var/lib/docker


    Then:

    sudo ls -al /<path of docker root dir>/volumes/portainer_data/_data


    Okey, i have removed portainer on the gui and installed it again but i have to same issue.


    I only could find this log of the portainer container



    Are there other logs what might help here?

    schmaex


    Hi,

    i don't know if you solved the issue but i previously had a similar one with a slow as f*** hard drive and usb sata hat.


    I did solve it with a boot delay in

    Code
    /boot/config.txt 

    with

    Code
    boot_delay=10

    for example, a 10 second delay. This gave my drives enough time to spin up until everything continued to boot.

    No but I haven't needed it on the CM4 boards I have. The RPi io board has both a 4 pin and a round plugin. So, it can use the floppy power connector on any atx psu. The axzez has a full motherboard header and can use any atx psu. The DeskPi Super6C doesn't have sata ports.

    ahh okey, so you are powering your board over the floppy power connector (Berg connector) (if the psu has a molex then over a molex to floppy adapter i guess) and your hard drives normally over sata power cables on the psu. (I guess there is no modification needed, just plug and play right?)

    Is there any issue on power draw of the CM4 module with board and the hard drives or is everything running safe? How much wattage the psu needs for the module with the board and 4 hdds? I don't want it to fry my board or the hard drives