Stefan Agner c6a1e668f4

Load loop module before starting the container (#824) ...

This makes sure that the kernel module loop is loaded, the loop devices
under /dev have been created before the container starts. Docker uses
the current /dev as template for the container /dev. If the loop entries
are missing, loop devices can't be used inside the container. Use
losetup which does not make assumption weather loop support is built-in.

This fixes issues seen on my machine when entering the build environment
the first time after build:
  mount: /mnt/data: failed to setup loop device for /export/data.ext4.
  make[2]: *** [package/pkg-generic.mk:364: /build/buildroot/output_rpi4/build/hassio-1.0.0/.stamp_target_installed] Error 32

2020-08-18 10:46:28 +02:00

..

enter.sh

Load loop module before starting the container (#824)

2020-08-18 10:46:28 +02:00

entry.sh

Fix boot (#459)

2019-08-28 10:32:46 +02:00

update-buildroot.sh

Fix linter

2020-07-22 17:53:10 +02:00

update-dtb.sh

Make machine-id persist (#649)

2020-05-04 15:11:43 +02:00

update-firmware-rpi.sh

Update kernel 20200702 (#757)

2020-07-02 11:28:39 +02:00

update-kernel-odroid.sh

Kernel improvments for Amlogic / Odroid (#747)

2020-06-27 10:48:08 +02:00

update-kernel-rpi.sh

Kernel updates (#643)

2020-04-29 11:16:38 +02:00

update-kernel-upstream.sh

Documentation (#769)

2020-08-03 16:31:36 +02:00