Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Unable to update because low space is reported...

Unable to update because low space is reported...

Scheduled Pinned Locked Moved Unsolved Support
3 Posts 2 Posters 13 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Online
    B Online
    Beardmann
    wrote last edited by
    #1

    Hi
    I have setup a fairly new installation on Ubuntu 24.04.2 LTS a base minimized install.
    I am on Cloudron version 9.0.6
    I have a 200GB disk which I use about 10% of, so nowhere near full.
    I have just setup email and one webmail application...

    Never the less I get this error as I try to update:

    box:tasks updating task 143 with: {"percent":1,"message":"Checking disk space"}
    Nov 19 21:57:47 box:shell df: df -B1 --output=source,fstype,size,used,avail,pcent,target /
    Nov 19 21:57:47 box:tasks setCompleted - 143: {"result":null,"error":{"message":"Not enough disk space. Updates require at least 2GB of free space. Available: 1.61GB","reason":"FileSystem Error"},"percent":100}
    Nov 19 21:57:47 box:tasks updating task 143 with: {"completed":true,"result":null,"error":{"message":"Not enough disk space. Updates require at least 2GB of free space. Available: 1.61GB","reason":"FileSystem Error"},"percent":100}
    Nov 19 21:57:47 box:taskworker Task took 0.045 seconds
    Nov 19 21:57:47 BoxError: Not enough disk space. Updates require at least 2GB of free space. Available: 1.61GB
    

    And here is what Ubuntu see...

    root@mail:# df -h
    Filesystem                         Size  Used Avail Use% Mounted on
    tmpfs                              1.6G  2.4M  1.6G   1% /run
    efivarfs                           256K   63K  189K  25% /sys/firmware/efi/efivars
    /dev/mapper/ubuntu--vg-ubuntu--lv  194G   18G  169G  10% /
    tmpfs                              7.9G     0  7.9G   0% /dev/shm
    tmpfs                              5.0M     0  5.0M   0% /run/lock
    /dev/sda2                          2.0G  192M  1.6G  11% /boot
    /dev/sda1                          1.1G  6.2M  1.1G   1% /boot/efi
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/84f24b757b9d84f88ff1ea3b4cfd9794b647233ae8ce868f2bc1d14c5a9cfea5/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/8c1f127a5eb1c459789e720b5e691b30106bd8215d484e734580a0f53683f038/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/461d38e9d745de889c78dd1205730e5857b9c42f237a7090020bcda57f890ad9/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/6ff8dafc4a68e9a23e7150f9b99d51bc5e23596f2aae354a5400cf3e06fc6fb6/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/7484467bc8771001d5c33663c3f2511966a4a7709ea8c11c0b8851835d73db73/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/beecafceb85397ed3feec60da9818a8296d97489a98d79bb3bffb97cf0f429df/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/0e3cc03e3499a83df17095fb7ed82ae8a7242ff29d2737390059812b88d35e3f/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/591bfec501f3dbde7a5260f5cfa4b4604a2925c85606737e0898c39b83a23971/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/bc4f5d327e0a565e4f518bf43a04ff1009a3e5ec5fa1fc32546f360c8c342973/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/f0eee6ebdac3fc41ac8dd9ccb550a4acd63ee942ddbe82559e9c0e7f0de49117/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/fce1b1a6e63eb255557a5bebf5b784ab9eacc8c0903b65a8287bd5d139180aa3/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/4c79e27e53b8bfa1cf5b1f7c92e3ee7b7520e820b63bbb08d2fb9d9b231000c6/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/4bb18472bb5a6f790408516877ca8272ad333f0d57b5c6dcb3bd00ae17a065fb/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/5d6479abaf9b5e14e10a3e3004e48ae0b4f172f9cfb5b24c67d2eda5258c455d/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/3919e9855fa1a162d52a00ae48305ea5f24ef3d3c4913ccd5c9e50e2c2d279d9/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/f91682163a94657121c295be69085becb32ae6dd6556fc8e20c7336532797f35/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/56563fcb79f8a6c31a34fa08ce994f72c07e62158aba7e43250fa28992e7fd1a/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/31f0f81d7f111405202f7189ae9a5a88c89710803a460b6fae218ff560d557f9/merged
    overlay                            194G   18G  169G  10% /var/lib/docker/overlay2/d9ec2a90080ec93141176aebde241a2fe91aaa15e14c9629400086dfc775beb7/merged
    tmpfs                              1.6G   12K  1.6G   1% /run/user/1000
    

    To me it looks like the update space check looks at tmpfs in order to get the 1.6GB? So maybe the script is "broken" somehow? Or am I missing something here?
    Maybe (just maybe) this could be because this is a minimized version of Ubuntu, maybe the "df" command is different some how to the one you get if you "unminimize" your installation...

    So here is the df details just in case...

    root@mail:# df --version
    df (GNU coreutils) 9.4
    

    /B

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote last edited by
      #2

      The code in question uses df -B1 --output=source,fstype,size,used,avail,pcent,target / to check the rootfs at /.
      Can you run that via SSH and see what that reports?

      B 1 Reply Last reply
      0
      • nebulonN nebulon

        The code in question uses df -B1 --output=source,fstype,size,used,avail,pcent,target / to check the rootfs at /.
        Can you run that via SSH and see what that reports?

        B Online
        B Online
        Beardmann
        wrote last edited by
        #3

        Can you run that via SSH and see what that reports?

        root@mail:/# df -B1 --output=source,fstype,size,used,avail,pcent,target /
        Filesystem                        Type    1B-blocks        Used        Avail Use% Mounted on
        /dev/mapper/ubuntu--vg-ubuntu--lv ext4 207953018880 18610241536 180670283776  10% /
        
        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search