OMV / root directory is ful, how can I delete them ?

1. offizieller Beitrag

    I deleted the some of contrainers and images, that' s ok now , thanks!


    root@openmediavault:/# df -h
    Filesystem Size Used Avail Use% Mounted on
    udev 981M 0 981M 0% /dev
    tmpfs 200M 22M 179M 11% /run
    /dev/sda1 14G 6.0G 7.1G 46% /
    tmpfs 999M 0 999M 0% /dev/shm
    tmpfs 5.0M 0 5.0M 0% /run/lock
    tmpfs 999M 0 999M 0% /sys/fs/cgroup
    tmpfs 999M 1.8M 997M 1% /tmp
    /dev/sdb1 1.8T 572G 1.3T 32% /srv/dev-disk-by-label-Vol02
    overlay 14G 6.0G 7.1G 46% /var/lib/docker/overlay2/bd37a5f0cd58212ef45fe660f57977173fe56dca0b63a67623c8f4bdabff292e/merged
    overlay 14G 6.0G 7.1G 46% /var/lib/docker/overlay2/75984e5723123b03262a24c0a9938bc6b09fd6d5a47a98298f8b0c1583690282/merged
    shm 64M 0 64M 0% /var/lib/docker/containers/bce4dc21b44a0c404c09e746f8d5107f5576a95c4f6ca0b618b51359ab2c140d/mounts/shm
    shm 64M 8.0K 64M 1% /var/lib/docker/containers/d55714fc684ed1bcb8f551d23115493d668bccb121d9d02fac469312583dc897/mounts/shm
    overlay 14G 6.0G 7.1G 46% /var/lib/docker/overlay2/f37f851900f9b3a7f91b745a197324c8c8079de6411cc3f01612f6bafb6ae670/merged
    shm 64M 0 64M 0% /var/lib/docker/containers/433c4fd8de96848f66bf29a4ac8fd2f699e76c50deb559276a248bfaa38405c8/mounts/shm


    root@openmediavault:/# docker system prune -a -f
    Deleted Networks:
    my-net
    WORKGROUP



    Total reclaimed space: 0B

    I deleted the some of contrainers and images, that' s ok now , thanks!


    root@openmediavault:/# df -h
    Filesystem Size Used Avail Use% Mounted on
    udev 981M 0 981M 0% /dev
    tmpfs 200M 22M 179M 11% /run
    /dev/sda1 14G 6.0G 7.1G 46% /




    root@openmediavault:/# docker system prune -a -f
    Deleted Networks:
    my-net
    WORKGROUP


    Total reclaimed space: 0B

    • Offizieller Beitrag

    To avoid filling root, you should avoid using /var/lib as storage for applications. The default settings of the docker plugin is to do that.


    You can change that by setting the docker base path to a share on another filesystem. There are a couple of threads here on how to move /var/lib/docker and change the docker base path. The should be very easy to find using the search function.

    • Offizieller Beitrag
    Zitat von Adoby

    To avoid filling root, you should avoid using /var/lib as storage for applications. The default settings of the docker plugin is to do that.


    You can change that by setting the docker base path to a share on another filesystem. There are a couple of threads here on how to move /var/lib/docker and change the docker base path. The should be very easy to find using the search function.

    I don't t think that changes the location of currently configured containers though, and he would essentially have to start over and set all of his containers up again.


    This is probably a case where dropping to command line if OP is comfortable, is best. Don't make any changes to the docker plugin and do the following.


    1. Assuming you can boot now, create a shared folder in the webUI.. ("Containers")
    2. SSH your server and become root.
    3. Stop Docker

    Code
    service docker stop


    4. Move your current docker folder to the new Container you created in the webUI --

    Code
    mv /var/lib/docker  /sharedfolders/Containers


    5. Create a link between /var/lib/docker and /sharedfolders/Containers


    Code
    ln -s /sharedfolders/Containers /var/lib/docker

    6. Restart Docker

    Code
    service docker start

    Now all of your containers/images will be stored in your "Containers" folder. I'm assuming your storage drives are much larger than your OS drive, so this won't be a problem anymore.

    • Offizieller Beitrag
    Zitat von rtibby

    Hm... I've done that ...


    Now all my containers are gone..... s**t ...


    Any way to restore my containers???

    Well this post is pretty old, but it still should have worked provided you modified it properly (ie, omv doesn't use /sharedfolders anymore by default)... when you say you "done all that"... what exactly did you do.

    So yes, I did replace /sharedfolders with one of my drive's absolute path, apart of that I did all steps detailed above.

    Indeed now the docker does not fill up the OS drive...


    The result was: all containers gone in Portainer.



    I did have like 10 containers, the most important ones Nexcloud, Nginx Proxy manager, Plex, Transmission...

    Now I am struggling to deploy again those, so far the stacks I used to deploy for various reasons none of them are working fine ....

    Especially latest Nextcloud version 22 doesn't work properly with latest MariaDB, no external drives can be added (it's a glitch) ... I'm getting the error "smbclient not installed" although I did install it ... Downgrading MariaDB to previous version did make the initialising of Nexcloud go through ... , still no luck with external drives


    Transmission_openVPN is giving errors like "AUTH_FAILED" even though I am using the right username/password for NORDVPN ...


    PS : Just managed to add Plex .... working OK.

    • Offizieller Beitrag

    If you know the absolute path to the folder you copied... just put that in the docker-plugin (I believe I wrote those before there was a issue using shared folders for containers.. before you could set the path in the docker plugin)

    Zitat von KM0201

    If you know the absolute path to the folder you copied... just put that in the docker-plugin (I believe I wrote those before there was a issue using shared folders for containers.. before you could set the path in the docker plugin)

    I did that ... Wasn't effective . I mean after doing it, there were still no containers showing in Portainer.


    Meanwhile, I am advancing with redeploying my containers .

    Managed to get Transmission under NORDVPN working ok.


    Going further to try to make Nextcloud to work.

    • Offizieller Beitrag

    You still haven't said what version of OMV you're using, so I'll assume 5


    SSH your server


    Check your docker root folder with this command

    Code
    docker info | grep Root


    and compare the path to the path in the webUI, and make sure they match.


    If they don't, fix it.


    Regardless, Restart docker

    Code
    systemctl restart docker

    No , they are not the same.

    The docker path is still "/var/lib/docker"


    But I executed the command to link the 2 folders as you mentioned in step 5 "Create a link between /var/lib/docker and /sharedfolders/Containers"

    Code : "ln -s /sharedfolders/Containers /var/lib/docker".


    And did started dockers as in Step 6.




    So with Step 5 above done, still the path of Docker in UI should point to the absolute path of my storage drive ?

    • Offizieller Beitrag

    I'm assuming you messed up the link somehow, I don't know... A symlink is not required. In the past w/ some previous versions, a symlink made this easier because of how the plugin was setup. It's not necessary now.


    Put the absolute path in the docker plugin, save, and restart docker.

    Zitat von KM0201

    I'm assuming you messed up the link somehow, I don't know... A symlink is not required. In the past w/ some previous versions, a symlink made this easier because of how the plugin was setup. It's not necessary now.


    Put the absolute path in the docker plugin, save, and restart docker.

    I do appreciate you are replying and trying to help, but it's too late now for that, I've already cleaned up the content of "/.../Containers" and went for fresh installs .


    It's ok, I am just figuring out one by one how to reinstall the dockers.

    For example, just figured out the latest Nextcloud image needs php 7.4, and I do have php 7.3 . That is why I presume was not working.

    So I am installing now the previous version of Nextcloud


    So, for the future use of docker path, I should still replace it now with the absolute path ? I am afraid now I will mess up with the fresh installed dockers...

    • Offizieller Beitrag

    I would, yes.


    Since you're apparently starting over as it is, there's no reason to use the symlink option (as I said, not necessary anymore anyway)... Just put the path in the docker plugin, save, and restart docker, and then verify with docker info that the path changed.

    Zitat von rtibby

    For example, just figured out the latest Nextcloud image needs php 7.4, and I do have php 7.3 . That is why I presume was not working.

    So I am installing now the previous version of Nextcloud

    Just to chime in on this one:


    If you're using Nextcloud on docker, you don't have to care about the php version.

    The image already has the proper version.


    From where did you saw the php 7.3 version?

    It is actually 7.4 version of PHP.


    So, I have BIG issues with Nextcloud .

    1. I did managed to install Nextcloud version 21, MariaDb, Letsencrypt.. managed to get it work .

    but , couldn't set external storage, there was a message like “smbclient” is not installed" . I did install it , but error did not go away

    2. I did try then do downgrade to previous Nextcloud versions which were ok .

    Normally Nextcloud does not allow you to downgrade ( database and version being different - didn't started)

    so, after hours of frustration, I did delete from my drive each every folder containing "nextcloud", than deployed from stack Nextcloud version 19


    I did delete all these folders:

    /srv/dev-disk-by-label-4TbDATA/AppData/Tibi/.docker/compose/.apps/nextcloud

    /srv/dev-disk-by-label-4TbDATA/data/database/nextcloud

    /srv/dev-disk-by-label-4TbDATA/data/nextcloud

    /srv/dev-disk-by-label-4TbDATA/data/nextcloud/data/.opcache/dc4c0df37060c310da66a4954f9ad32c/data/nextcloud

    /srv/dev-disk-by-label-4TbDATA/config/www/SupportedApps/Nextcloud

    /srv/dev-disk-by-label-4TbDATA/config/www/rtibby.com/SupportedApps/Nextcloud



    Containers started, but nextcloud container did not :


    Initializing nextcloud 19.0.13.1 ...,

    Initializing finished,

    New nextcloud instance,

    AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.23.0.5. Set the 'ServerName' directive globally to suppress this message,

    AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.23.0.5. Set the 'ServerName' directive globally to suppress this message,

    [Sat Oct 23 12:15:18.958704 2021] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.4.21 configured -- resuming normal operations,

    [Sat Oct 23 12:15:18.958762 2021] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND',

    172.23.0.2 - - [23/Oct/2021:12:16:02 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:16:04 +0100] "GET /favicon.ico HTTP/1.1" 404 674 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:17:00 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:17:01 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:17:08 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:17:09 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:18:01 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    172.23.0.2 - - [23/Oct/2021:12:18:30 +0100] "GET / HTTP/1.1" 500 717 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36",

    [Sat Oct 23 12:18:47.306620 2021] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully,

    AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.23.0.5. Set the 'ServerName' directive globally to suppress this message,

    AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.23.0.5. Set the 'ServerName' directive globally to suppress this message,

    [Sat Oct 23 12:18:52.658741 2021] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.4.21 configured -- resuming normal operations,

    [Sat Oct 23 12:18:52.658791 2021] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND',

    172.23.0.2 - - [23/Oct/2021:12:19:34 +0100] "GET / HTTP/1.1" 500 717 "-" "python-requests/2.21.0",

    172.23.0.2 - - [23/Oct/2021:12:19:36 +0100] "GET / HTTP/1.1" 500 717 "-" "python-requests/2.21.0",

    172.23.0.2 - - [23/Oct/2021:12:19:37 +0100] "GET / HTTP/1.1" 500 717 "-" "python-requests/2.21.0",


    Any ideas how to have again a working Nextcloud docker ? (apart of reinstalling OMV5 itself ?)

    How are you installing Nextcloud???


    From the look of it, your not doing it on docker!!!

    Or, at least, not using the image from linuxserver.


    And NC v19 has reached EOL (End Of Life) 19.0.13 (2021-07-01)


    Go here and follow this guide to have it up and running in no time (and with the plus that everybody that can help, know the steps you take)

    [How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose - Guides - openmediavault

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden