diff mbox series

Dockerfile.isar: Pull qemu-user-static from buster-backports

Message ID 16ff005a-fcfe-1cea-b461-b9759a1cfa97@siemens.com
State Superseded, archived
Headers show
Series Dockerfile.isar: Pull qemu-user-static from buster-backports | expand

Commit Message

Jan Kiszka Sept. 22, 2020, 11:56 p.m. UTC 
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.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 Dockerfile.isar | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Comments

Jan Kiszka Sept. 24, 2020, 1:14 a.m. UTC | #1 
On 23.09.20 09:56, [ext] Jan Kiszka wrote:
> 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.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>   Dockerfile.isar | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Dockerfile.isar b/Dockerfile.isar
> index 6b325f3..739dfab 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 binfmt-support\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 \
> 

This one triggers in a strange way an very strange issue: Running 
debootstrap (even directly, without Isar) in this new container will 
make the container's /proc and possibly other mounts disappear.

I tried to dig down to this from the changes above but failed. I'm now 
analyzing what happens in debootstrap, and why it picks the host mounts, 
rather than that of the new rootfs. Any ideas welcome.

Jan
diff mbox series

Patch

diff --git a/Dockerfile.isar b/Dockerfile.isar
index 6b325f3..739dfab 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 binfmt-support\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 \