qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docke


From: Fam Zheng
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images
Date: Fri, 8 Jul 2016 17:14:16 +0800
User-agent: Mutt/1.6.1 (2016-04-27)

On Fri, 07/08 08:53, Alex Bennée wrote:
> 
> Fam Zheng <address@hidden> writes:
> 
> > On Tue, 06/28 16:42, Alex Bennée wrote:
> >> This is the latest iteration of my qemu-user support inside Docker.
> >> They apply directly on top of master. I've made the changes suggested
> >> in the last review and split apart another patch. I've also added a
> >> new update command so a tagged image can be updated with the latest
> >> QEMU.
> >>
> >> To use, first ensure you build the debian-bootstrap image:
> >>
> >>     DEB_ARCH=armhf DEB_TYPE=testing \
> >>       ./tests/docker/docker.py build qemu:debian-bootstrap \
> >>       ./tests/docker/dockerfiles/debian-bootstrap.docker \
> >>       --include-executable=./arm-linux-user/qemu-arm
> >
> > Alex,
> >
> > Sorry for the late reply.
> >
> > Is there a way to setup or detect the binfmt_misc configuration on the
> > system?
> 
> The trick is doing this in a distribution agnostic way. Certainly
> Debian-a-like systems have scripts that allow you to query the state of
> binmfmt_misc.

What about changing the docker file from "FROM scratch" to "FROM debian"? Then
I think you can query the state in the container. (What is the query command
called, BTW?)

In addition, what about the idea I proposed in v2: moving the debootstrap
command to a dockerfile "RUN" directive? Does it work?  I can experiment with
that in this weekend, but if you know that already, that's even better. I think
one hurdle in this series is the required build step.

Fam



reply via email to

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