From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7024078985875161088 X-Received: by 2002:a1c:4c17:: with SMTP id z23mr14096705wmf.61.1635441636658; Thu, 28 Oct 2021 10:20:36 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:19d0:: with SMTP id u16ls3842371wmq.3.canary-gmail; Thu, 28 Oct 2021 10:20:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJybi94KK2yNxmGWHqvG/JE0Glr6mf1ilPUMk9rXICMIZCVdOFs3wAGziG+7IV+YoqLZFTI0 X-Received: by 2002:a1c:7dca:: with SMTP id y193mr5828972wmc.18.1635441635767; Thu, 28 Oct 2021 10:20:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635441635; cv=none; d=google.com; s=arc-20160816; b=ucMQstYfepvMq+I7/Lq1kKnH0aNioELpLAFMXVv9AgZatL1l4UuyXBDgtVl+tDH0bt SnB+ce1gA6PcC8rUidnI2P+iVyWk5P3Gam3jFIIK4qc6vPgqZf82k+OYQptGg4tiSyZ3 D2qK8xY83smXd5wMMQjOUhHCXxaGkKKLd2yqhnfLlr6pdtzOQhpOB6/XNLr2xNXdgnlB 9eEYRGQUHzxn1bXvcN65CmKX0IMycZK2KfuHy+O3zNdCgjIy/H5NkzrrjaFDdWXpISTz VeDVBpb9neWTyobpybwMoLsp0gtw5PC7egFELj2h9eYp8ScAki9GpIZF2fjxfM9ILXUz XYgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=eX4lUmtB5CNt3mdGdxqREvwZI1PglDeVRw/hlaSXpp8=; b=Z9Ch5eYU0xSAB9IOkt3iM69CGEMPI2f6oEr4huD1MzVZdi7PjGV+KFC38OMAbU25+Y L6w3BroyVnAat9bOSJcCkmc3s5PEooXE3zg+3dyucVBzKrWJpjuX7aIxZadnT2vDnxav qL9ma+fABhov2uY0zs3NIXphSgHJMN5NYeO3fxNJEdaeS39TDeHQk2LudkF5pAw/jxpr T/bWCoZODzScprK0znYf2RMcNIEYLYRMDVUCJ70LG/gXZWMQvLtS53p4WFE5L6aiuxOn w/4zznQkKC5up31u2m11pMYKHfm/R3lsVSM3N6wsK+w+xCKHTyOONmXLzBuIGdSrGMBv UX/g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id o30si749319wms.2.2021.10.28.10.20.35 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Oct 2021 10:20:35 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id 19SHKZrU018664 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 28 Oct 2021 19:20:35 +0200 Received: from md1za8fc.ad001.siemens.net ([167.87.32.106]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 19SHKYGh022981; Thu, 28 Oct 2021 19:20:35 +0200 Date: Thu, 28 Oct 2021 19:20:33 +0200 From: Henning Schild To: Jan Kiszka Cc: Subject: Re: new movement in binfmt_misc namespace discussion on lkml Message-ID: <20211028192033.2a1a4f14@md1za8fc.ad001.siemens.net> In-Reply-To: <148c4212-557b-75ef-ed43-d9295ed5ed80@siemens.com> References: <20211028133348.64931b7b@md1za8fc.ad001.siemens.net> <148c4212-557b-75ef-ed43-d9295ed5ed80@siemens.com> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: 3heJlEsrVyVN Am Thu, 28 Oct 2021 17:42:20 +0200 schrieb Jan Kiszka : > 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 >