[PATCH v2 2/3] Azure: Add fuse device for test.py tests

Alper Nebi Yasak alpernebiyasak at gmail.com
Sun Jun 13 16:07:29 CEST 2021

The EFI secure boot and capsule test setups need to prepare disk images
for their tests using virt-make-fs, which requires access to the host
fuse device. This is not exposed to the docker container by default and
has to be added explicitly. Add it.

Signed-off-by: Alper Nebi Yasak <alpernebiyasak at gmail.com>

Changes in v2:
- Always pass in /dev/fuse to Azure's docker run invocation.

 .azure-pipelines.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 35ab7f30b276..976868dd2eb7 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -318,7 +318,8 @@ jobs:
           # as sandbox testing need create files like spi flash images, etc.
           # (TODO: clean up this in the future)
           chmod 777 .
-          docker run -v $PWD:$(work_dir) $(ci_runner_image) /bin/bash $(work_dir)/test.sh
+          # Some tests using libguestfs-tools need the fuse device to run
+          docker run --device /dev/fuse:/dev/fuse -v $PWD:$(work_dir) $(ci_runner_image) /bin/bash $(work_dir)/test.sh
   - job: build_the_world
     displayName: 'Build the World'

More information about the U-Boot mailing list