Do not search qemu binary when docker is in use

When executing a sparc64 qemu job with docker, LAVA throws an
infrastructure error by not finding the qemu binary.
This is normal since the binary will be in the docker image.

So when actions/boot/qemu is used with the optional docker, dont try to
find the qemu binary.

Signed-off-by: Corentin LABBE <clabbe@baylibre.com>
16 jobs for qemu-docker-no-binary in 14 minutes and 8 seconds (queued for 3 seconds)
Status Job ID Name Coverage
  Test
passed #121633
amd64
dispatcher-debian-10

00:04:27

passed #121635
amd64
dispatcher-debian-11

00:04:46

passed #121634
amd64
server-debian-10

00:05:05

passed #121636
amd64
server-debian-11

00:07:38

 
  Analyze
passed #121637
amd64-dind
bandit-sast

00:01:01

passed #121638
amd64
black

00:00:34

passed #121639
amd64
code_quality

00:00:22

passed #121644
amd64
codespell

00:00:20

passed #121640
amd64
coverage

00:06:26

60.97%
failed #121641
amd64
dockerfiles

00:00:12

passed #121643
amd64
pylint

00:03:08

passed #121642
amd64
schemas

00:00:31

 
  Build
skipped #121646
amd64
debian/10
skipped #121645
amd64
doc
skipped #121647
amd64-dind
docker-amd64-dispatcher
skipped #121648
amd64-dind
docker-amd64-server
 
Name Stage Failure
failed
dockerfiles Analyze There has been a runner system failure, please try again
Removing tests/lava_scheduler_app/__pycache__/
Removing tests/lava_server/__pycache__/
Removing tests/linaro_django_xmlrpc/__pycache__/
Removing tmp/

Skipping Git submodules setup
Executing "step_script" stage of the job script
Cleaning up file based variables
ERROR: Job failed (system failure): Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/61fe9e03f438546845dbb3c931c8541e827d81234f3dce7e301508bac410cecc/merged: device or resource busy (docker.go:757:0s)