failed to write (No space left on device) error in image creation via DIB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
diskimage-builder |
New
|
Undecided
|
Unassigned |
Bug Description
I have installed DIB in a ppc64le openstack environment which is non- KVM. I have installed multiple dependencies in this env for DIB to work. Finally DIB does workin virtual env but I am running into no disk space issue with minimal or more elements always
DIB installed at:
(env) neo@neo:
/home/neo/
df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1202368 0 1202368 0% /dev
tmpfs 251328 42176 209152 17% /run
/dev/mapper/
tmpfs 1256576 0 1256576 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1256576 0 1256576 0% /sys/fs/cgroup
/dev/md0 475434 69793 376576 16% /boot
/dev/mapper/
/dev/mapper/
/dev/mapper/
tmpfs 251328 0 251328 0% /run/user/1000
Running commands similar to
(env)/dib/env/bin$ sudo ./disk-image-create -a ppc64el -o ubuntu-vm3 -t raw -x vm ubuntu --logfile diblog.txt
Getting error exit 1
2018-04-24 09:26:18.661 | > Unpacking linux-image-
2018-04-24 09:26:18.661 | > dpkg: error processing archive /var/cache/
2018-04-24 09:26:18.661 | > cannot copy extracted data for './lib/
2018-04-24 09:26:18.661 | > No apport report written because the error message indicates a disk full error
2018-04-24 09:26:18.661 | > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
2018-04-24 09:26:18.661 | > Examining /etc/kernel/
2018-04-24 09:26:18.661 | > run-parts: executing /etc/kernel/
2018-04-24 09:26:18.661 | > Selecting previously unselected package linux-image-
2018-04-24 09:26:18.661 | > Preparing to unpack .../linux-
2018-04-24 09:26:18.661 | > Unpacking linux-image-
2018-04-24 09:26:18.661 | > dpkg: error processing archive /var/cache/
Attaching log
It is probably trying to build in a tmpfs? See https:/ /docs.openstack .org/diskimage- builder/ latest/ user_guide/ building_ an_image. html#speedups
I suggest exporting DIB_NO_TMPFS=1 into the environment to stop this
This has been a point of confusion before. I'm wondering if we should turn this off by default