Dockerfile.isar: Adjust binfmt setup for qemu-user-static
It turned out [1] that our current way of setting up binfmt_misc during container start does not reliably work, namely does not overwrite incompatible host settings. Running dpkg-reconfigure solves this. To avoid confusing warnings of the kind update-binfmts: warning: qemu-aarch64 already enabled in kernel. we filter them out. That will continue to flood the console with warnings in case the container is started without privileges. [1] https://groups.google.com/forum/#!msg/isar-users/2G-Diz0BR1Y/Y0X6eHggCgAJ Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com>
This commit is contained in:
parent
6fdbe299a4
commit
2fc711a459
@ -20,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\nupdate-binfmts --enable|" /kas/docker-entrypoint
|
||||
RUN sed -i 's|#!/bin/bash|\0\n\ndpkg-reconfigure qemu-user-static 2>\&1 \| grep -v "already enabled in kernel"|' /kas/docker-entrypoint
|
||||
|
Loading…
Reference in New Issue
Block a user