qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile


From: Fam Zheng
Subject: Re: [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile
Date: Fri, 5 May 2017 17:12:40 +0800
User-agent: Mutt/1.8.0 (2017-02-23)

On Fri, 05/05 09:27, Alex Bennée wrote:
> 
> Fam Zheng <address@hidden> writes:
> 
> > Some by default blocked syscalls are required to run tests for example
> > userfaultfd.
> 
> Is there any way the tests could DoS the host? I guess you could achieve
> the same running the iotests directly from make but it does seem we
> should confine the docker guest as much as possible.

I don't know the answer to the security question, but if a confined docker
environment is full of pitfalls and unpleasant to work with, it won't grow that
much.

Patchew runs this in a VM, so it's not a big problem to me.

> 
> >
> > Signed-off-by: Fam Zheng <address@hidden>
> > ---
> >  tests/docker/Makefile.include | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> > index 0ed8c3d..09d157c 100644
> > --- a/tests/docker/Makefile.include
> > +++ b/tests/docker/Makefile.include
> > @@ -127,6 +127,7 @@ docker-run: docker-qemu-src
> >     $(call quiet-command,                                           \
> >             $(SRC_PATH)/tests/docker/docker.py run                  \
> >                     $(if $(NOUSER),,-u $(shell id -u)) -t           \
> > +                   --security-opt seccomp=unconfined               \
> >                     $(if $V,,--rm)                                  \
> >                     $(if $(DEBUG),-i,--net=none)                    \
> >                     -e TARGET_LIST=$(TARGET_LIST)                   \
> 
> 
> --
> Alex Bennée



reply via email to

[Prev in Thread] Current Thread [Next in Thread]