From: Jan Kiszka <jan.kiszka@siemens.com>
To: kas-devel <kas-devel@googlegroups.com>
Cc: isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: [PATCH v2] Dockerfile.isar: Pull qemu-user-static from buster-backports
Date: Thu, 24 Sep 2020 13:12:35 +0200 [thread overview]
Message-ID: <8d2408ef-899f-8479-7674-eb344da2bb85@siemens.com> (raw)
In-Reply-To: <16ff005a-fcfe-1cea-b461-b9759a1cfa97@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
This is needed for running fakeroot from bullseye and sid which triggers
an unimplemented syscall with the current version.
Due to changes in the new qemu-user-static package, the current approach
to activate its binfmt settings no longer works. Instead, switch to an
explicit call of the binfmt-support in init script.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
Changes in v2:
- fix binfmt activation
- drop unneeded (and effectless) listing of binfmt-support for
buster-backports
OK, this was a nice one:
- debootstrap (of buster) creates the rootfs initially with a link of
$target/proc -> /proc
- later, it tries to umount $target/proc (and then sets up a proper
mounting via chroot) - I consider this a bug of debootstrap
- for us, umount $target/proc, which is effectively umount /proc,
because /proc/sys/fs/binfmt_misc is mounted
- debootstrap ignores this error
- but due to the issue in v1, binfmt_misc wasn't mounted, and the
problem started...
Dockerfile.isar | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Dockerfile.isar b/Dockerfile.isar
index 6b325f3..cde63b0 100644
--- a/Dockerfile.isar
+++ b/Dockerfile.isar
@@ -3,7 +3,9 @@
FROM kasproject/kas:latest
ENV LC_ALL=en_US.UTF-8
-RUN apt-get update && \
+RUN echo 'deb http://deb.debian.org/debian buster-backports main' > /etc/apt/sources.list.d/buster-backports.list && \
+ echo "Package: qemu-user-static\nPin: release n=buster-backports\nPin-Priority: 501\n\nPackage: *\nPin: release n=buster-backports\nPin-Priority: -1" > /etc/apt/preferences.d/qemu-user-static && \
+ apt-get update && \
apt-get install -y -f --no-install-recommends \
autoconf automake gdisk libtool bash-completion \
sudo grub2 grub-efi-amd64-bin grub-efi-ia32-bin \
@@ -18,4 +20,4 @@ RUN echo "builder ALL=NOPASSWD: ALL" > /etc/sudoers.d/builder-nopasswd && \
RUN echo "Defaults env_keep += \"ftp_proxy http_proxy https_proxy no_proxy\"" \
> /etc/sudoers.d/env_keep && chmod 660 /etc/sudoers.d/env_keep
-RUN sed -i 's|#!/bin/bash|\0\n\ndpkg-reconfigure qemu-user-static 2>\&1 \| grep -v "already enabled in kernel"|' /kas/docker-entrypoint
+RUN sed -i 's|#!/bin/bash|\0\n\n/etc/init.d/binfmt-support start|' /kas/docker-entrypoint
--
2.26.2
next prev parent reply other threads:[~2020-09-24 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 7:56 [PATCH] " Jan Kiszka
2020-09-24 9:14 ` Jan Kiszka
2020-09-24 11:12 ` Jan Kiszka [this message]
2020-09-24 11:52 ` [PATCH v2] " Henning Schild
2020-09-24 14:50 ` Jan Kiszka
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=8d2408ef-899f-8479-7674-eb344da2bb85@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.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