public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: new movement in binfmt_misc namespace discussion on lkml
Date: Thu, 28 Oct 2021 19:20:33 +0200	[thread overview]
Message-ID: <20211028192033.2a1a4f14@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <148c4212-557b-75ef-ed43-d9295ed5ed80@siemens.com>

Am Thu, 28 Oct 2021 17:42:20 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> On 28.10.21 13:33, Henning Schild wrote:
> > If that ever makes it into the kernel Isar might maybe get away with
> > running in a "regular" container, or will get a step closer.
> > 
> > https://lkml.org/lkml/2021/10/28/274
> > 
> > I have been involved a pretty long time ago, now the topic is
> > coming up again with a new player having taken over the patches and
> > proposing the again.
> > 
> > Let us see how it goes this time.
> > Henning
> >   
> 
> This is great news. I just had to help a user this morning once again
> with fighting away outdated Ubuntu qemu-user-static on the host to
> make bullseye's version effective inside the container.
> 
> Did you already check what will then be needed on top to make
> podman/docker/etc able to use that feature?

No that just came in today. I might give it a go at some point. But
while the procedure is not complicated it will take several hours
anyhow.

I thought about getting back to the guy already to "promise testing",
just to strengthen the thread. But doing that i could also stall it,
not knowing when i get around to testing.
Maybe just strengthen the need again, but he has a good list of refs
under the pretty longish commit messages.

Henning

> Jan
> 


      reply	other threads:[~2021-10-28 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 11:33 Henning Schild
2021-10-28 15:42 ` Jan Kiszka
2021-10-28 17:20   ` Henning Schild [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=20211028192033.2a1a4f14@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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