From: Daniel Wagner <wagi@monom.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kas-devel <kas-devel@googlegroups.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] docker: Add binfmt-support for Isar cross-building
Date: Wed, 06 Sep 2017 17:26:20 +0200 [thread overview]
Message-ID: <87fubzg86b.fsf@helium.monom.org> (raw)
In-Reply-To: <3edc2496-a39d-bb6d-25da-b9760eebbae0@siemens.com> (Jan Kiszka's message of "Tue, 5 Sep 2017 11:00:28 +0200")
Hi Jan,
Jan Kiszka <jan.kiszka@siemens.com> writes:
> On 2017-09-05 10:58, [ext] Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Additionally requires to run the container with --privileged - not nice but
>> unavoidable right now, see also
>> https://groups.google.com/forum/#!topic/isar-users/Un75m49InjY
>>
>> Also note that running containers with different binfmt settings
>> concurrently will cause troubles. Same for the case that the host
>> requires deviating settings. Use carefully.
Patch applied on next.
Thanks,
Daniel
prev parent reply other threads:[~2017-09-06 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 8:58 Jan Kiszka
2017-09-05 9:00 ` Jan Kiszka
2017-09-06 15:26 ` Daniel Wagner [this message]
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=87fubzg86b.fsf@helium.monom.org \
--to=wagi@monom.org \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kas-devel@googlegroups.com \
/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