From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, riku.voipio@linaro.org
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 [thread overview]
Message-ID: <20160708091416.GB8848@ad.usersys.redhat.com> (raw)
In-Reply-To: <8737nkmup5.fsf@linaro.org>
On Fri, 07/08 08:53, Alex Bennée wrote:
>
> Fam Zheng <famz@redhat.com> 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
next prev parent reply other threads:[~2016-07-08 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 15:42 [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 1/5] tests/docker/docker.py: docker_dir outside build Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 2/5] tests/docker/docker.py: support --include-executable Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 3/5] tests/docker/docker.py: check and run .pre script Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 4/5] tests/docker/dockerfiles: new debian-bootstrap.docker Alex Bennée
2016-06-28 15:42 ` [Qemu-devel] [PATCH v3 5/5] tests/docker/docker.py: add update operation Alex Bennée
2016-07-08 6:15 ` [Qemu-devel] [PATCH v3 0/5] Support building qemu-user powered docker test images Fam Zheng
2016-07-08 7:53 ` Alex Bennée
2016-07-08 9:14 ` Fam Zheng [this message]
2016-07-08 10:10 ` Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160708091416.GB8848@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).