[lmi] dpkg error on redhat server

[Greg Chicares]

Vadim--Please let me know your thoughts on the question at the
bottom.

I've transplanted the proven lmi installation on centos to a
corporate redhat server, and after these commands that succeed:

+ dpkg --add-architecture i386
+ apt-get update

this one fails:

+ apt-get --assume-yes install wget g++-mingw-w64 automake libtool make 
pkg-config git cvs zsh bzip2 unzip sudo wine default-jre jing trang 
g++-multilib libxml2-utils libxslt1-dev vim-gtk vim-doc shellcheck bc 
libarchive-tools xsltproc

as follows:

dpkg: error processing archive 
/tmp/apt-dpkg-install-g8ZMwE/216-iso-codes_4.3-1_all.deb (--unpack):
 cannot copy extracted data for 
'./usr/share/locale/fo/LC_MESSAGES/iso_3166-1.mo' to '/usr/share/lo
cale/fo/LC_MESSAGES/iso_3166-1.mo.dpkg-new': failed to write (No space left on 
device)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

and similarly for several other archives, then finally:

dpkg: unrecoveraE: Write error - write (28: No space left on device)
E: Sub-process /usr/bin/dpkg returned an error code (2)

Investigating:

$df --si
Filesystem                         Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-lv_root     4.3G  4.3G  377k 100% /
devtmpfs                           8.4G     0  8.4G   0% /dev
tmpfs                              8.4G     0  8.4G   0% /dev/shm
tmpfs                              8.4G  458M  7.9G   6% /run
tmpfs                              8.4G     0  8.4G   0% /sys/fs/cgroup
/dev/mapper/VolGroup00-lv_usr      7.6G  6.5G  1.1G  87% /usr
/dev/sda1                          1.1G  186M  768M  20% /boot
/dev/mapper/VolGroup00-lv_var      4.3G  1.4G  3.0G  31% /var
/dev/mapper/VolGroup00-lv_home     2.2G  195M  2.0G  10% /home
/dev/mapper/VolGroup00-lv_var_log  2.2G  174M  2.0G   9% /var/log
/dev/mapper/VolGroup00-lv_tmp      4.3G  1.4G  3.0G  32% /tmp
/dev/mapper/VolGroup00-lv_opt      4.3G  1.5G  2.9G  33% /opt
tmpfs                              1.7G     0  1.7G   0% /run/user/19193
tmpfs                              1.7G     0  1.7G   0% /run/user/0
tmpfs                              1.7G     0  1.7G   0% /run/user/65345

$df --inodes
Filesystem                         Inodes  IUsed   IFree IUse% Mounted on
/dev/mapper/VolGroup00-lv_root      65824  65063     761   99% /
devtmpfs                          2027347    442 2026905    1% /dev
tmpfs                             2030971      1 2030970    1% /dev/shm
tmpfs                             2030971   1482 2029489    1% /run
tmpfs                             2030971     16 2030955    1% /sys/fs/cgroup
/dev/mapper/VolGroup00-lv_usr     2174120 180297 1993823    9% /usr
/dev/sda1                           65536    343   65193    1% /boot
/dev/mapper/VolGroup00-lv_var     2097152  12406 2084746    1% /var
/dev/mapper/VolGroup00-lv_home    1048576   5959 1042617    1% /home
/dev/mapper/VolGroup00-lv_var_log 1048576    242 1048334    1% /var/log
/dev/mapper/VolGroup00-lv_tmp     2097152    536 2096616    1% /tmp
/dev/mapper/VolGroup00-lv_opt     2097152  43469 2053683    3% /opt
tmpfs                             2030971      1 2030970    1% /run/user/19193
tmpfs                             2030971      1 2030970    1% /run/user/0
tmpfs                             2030971      1 2030970    1% /run/user/65345

On my own machine, I have:

/home/greg[0]$ df --si /srv/chroot/bullseye0      
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb5       129G   56G   67G  46% /
/home/greg[0]$ df --inodes /srv/chroot/bullseye0 
Filesystem      Inodes  IUsed   IFree IUse% Mounted on
/dev/sdb5      8019968 848531 7171437   11% /

and it looks like a freshly-constructed bullseye chroot where
lmi has been built needs more than nine gibibytes:

/root[0]# du -sb /srv/chroot/lmi_bullseyeeraseme            
9315886040      /srv/chroot/lmi_bullseyeeraseme

Vadim--do you suppose it's worth trying to work around this, e.g.
by replacing
  apt-get install pkg1 pkg2 pkg3
with
  apt-get install pkg1
  apt-get install pkg2
  apt-get install pkg3
after perhaps cd'ing to /tmp (tmpfs seems to have some space), or
does this server just need to have a lot of disk capacity added?