f35aace69f
The loopback handling in the Linux kernel limits the filenames of files associated to loopback devices, see also linux/loop.h. This is reflected also on userspace, as kpartx will silently do nothing (exiting with 0) when requesting to remove a filename longer than 64 characters, as that name will obviously not match the truncated filename. The result of this is that, when extracting qcow2 images for the first time, if the qcow2 filename is long enough then the loopback device will not be removed, remaining as stale in the host. As a workaround, use a temporary file name when convering a qcow2 image to raw, instead of using the base name of the qcow2 file. While this still will not fix the issue when manually using a long temporary directory (e.g. TMP_DIR=/very/long/etc...), at least should avoid it in other cases. Change-Id: Ibf46cd313a9d89412c0e1068fa0993be6c5a29db |
||
---|---|---|
.. | ||
environment.d | ||
root.d | ||
element-deps | ||
element-provides | ||
package-installs.yaml | ||
README.rst |
=========== ubuntu-core =========== Use Ubuntu Core cloud images as the baseline for built disk images. Overrides: * To use a non-default URL for downloading base Ubuntu cloud images, use the environment variable DIB\_CLOUD\_IMAGES * To download a non-default release of Ubuntu cloud images, use the environment variable DIB\_RELEASE * To use different mirrors rather than the default of archive.ubuntu.com and security.ubuntu.com, use the environment variable DIB\_DISTRIBUTION\_MIRROR