Actual space reported by system and Docker

[catthehacker]

I'm trying to build Docker image in GH Actions but it fails to commit it due to insufficient space which seems weird since I have 60GB+ of free space and I have confirmed locally that image doesn't exceed 45GB
https://github.com/catthehacker/virtual-environments/runs/3138234311

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        84G   22G   62G  27% /
devtmpfs        3.4G     0  3.4G   0% /dev
tmpfs           3.4G   12K  3.4G   1% /dev/shm
tmpfs           696M  1.1M  695M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.4G     0  3.4G   0% /sys/fs/cgroup
/dev/loop0       56M   56M     0 100% /snap/core18/2066
/dev/loop1       56M   56M     0 100% /snap/core18/2074
/dev/loop2       71M   71M     0 100% /snap/lxd/21029
/dev/loop3       68M   68M     0 100% /snap/lxd/20326
/dev/loop4       33M   33M     0 100% /snap/snapd/12398
/dev/sdb15      105M  7.9M   97M   8% /boot/efi
/dev/loop5       33M   33M     0 100% /snap/snapd/12159
/dev/sda1        14G  4.1G  9.0G  32% /mnt

packer build:

==> packer-ubuntu-20.04: Provisioning with shell script: /home/runner/work/virtual-environments/virtual-environments/images/linux/scripts/installers/cleanup.sh
    packer-ubuntu-20.04: Before: 14345 MB
    packer-ubuntu-20.04: After : 16790 MB
    packer-ubuntu-20.04: Delta : 2445 MB
[...]
    packer-ubuntu-20.04: Available disk space: 19772 MB
    packer-ubuntu-20.04: Skipping validation disk space...
==> packer-ubuntu-20.04: Committing the container
==> packer-ubuntu-20.04: Error committing container: exit status 1
==> packer-ubuntu-20.04: Stderr: Error response from daemon: ApplyLayer exit status 1 stdout:  stderr: write /usr/local/lib/android/sdk/build-tools/30.0.1/lib64/libclang_android.so: no space left on device

Is there some kind of special configuration on runners or is that fault of remote storage on Azure VMs?

[miketimofeev]

@catthehacker we're not aware of any special configuration 🤔 Maybe docker creates some temporary files during the build so 62 is not enough? Do you have a chance to create a VM in Azure and test the same build there?

[catthehacker]

I can, but forgot about one thing, when building Docker + Packer it uses live container to run everything and then commit it so running container size (~40GB) + committed image size (~40GB). With Docker only it commits layers sequentially per executed command. Sorry for the noise 🐈