Docker build fails with Clear Containers as default

[jcvenegas]

When using osbuilder and docker use cc-oci-runtime as default runtime, it breaks with a segfault issue caused by qemu.

To workaround this it is need to use runc as default runtime (docker does not give an option to use change a runtime using docker build command)

The issue intel/cc-oci-runtime#669 need to be fixed to work correctly with cc-oci-runtime as default runtime.

[grahamwhaley]

I also suspect we won't work under Docker with a cc-runtime due to the --privileged line here as well.
When I ran it (sort of by accident ;-)), I didn't get the qemu error, I get a mmap error more like:

17:26:17 Step 2/9 : RUN dnf install -y qemu-img parted gdisk make gcc bc git e2fsprogs libudev-devel pkgconfig
17:26:17  ---> Running in 6220fc9fd574
17:26:25 �[91mBDB0126 mmap: Invalid argument
17:26:25 �[0m�[91mhandle_proxy_response:616:Error response received from proxy at /run/virtcontainers/pods/6220fc9fd574d56d747fe5bcd635ae18ab67dc190fca8e4b97b6a9dda0e08d2f/proxy.sock: {"msg":"vm: unknown token 7yumQLpbAES-kAnPNgsZZswCu_WH7hkFBnhpKa-bMqg="}
17:26:25 
17:26:25 /usr/libexec/clear-containers/cc-shim: Shim received an error in responseto ConnectShim command, exiting�[0mThe command '/bin/sh -c dnf install -y qemu-img parted gdisk make gcc bc git e2fsprogs libudev-devel pkgconfig' returned a non-zero code: 1
17:26:25 Makefile:114: recipe for target 'docker-build' failed