SiegfriedSiegert/PTU5KAS
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1988cdd26b
PTU5KAS/Dockerfile.isar

22 lines
894 B
Docker
Raw Normal View History

Docker: Update to Debian stretch Time to move forward, buster is almost in sight. We may break some older Yocto versions this way, but they can always use older images. Along this update, this migrates the locale setup towards the recommendation on https://docs.docker.com/samples/library/debian/#locales. Furthermore, DEBIAN_FRONTEND=noninteractive is moved to the top-level Dockerfile - it's generic. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2018-07-17 21:56:15 +02:00
# This image builds Isar jobs using the kas tool
Add Dockerfile for Isar image builder Isar requires a number of extra packages compared to a Yocto build. It also needs a newer e2fsprogs version which can be taken from backports. Last but not least, its keystone multistrap contains a nasty bug [1] under in jessie so that we need to pull the updated version from stretch. The value of having this image still based on jessie is that it can be used for both purposes: Yocto (2.1/2.2) and Isar builds. We push it along the kas core image as kas-isar during the CI run. Isar still requires some raised privileges. Therefore, the image has to be started with the additional switches "--cap-add=SYS_ADMIN --cap-add=MKNOD --device $(/sbin/losetup -f)". [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774698 Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-28 19:25:58 +02:00
Docker: Update to Debian stretch Time to move forward, buster is almost in sight. We may break some older Yocto versions this way, but they can always use older images. Along this update, this migrates the locale setup towards the recommendation on https://docs.docker.com/samples/library/debian/#locales. Furthermore, DEBIAN_FRONTEND=noninteractive is moved to the top-level Dockerfile - it's generic. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2018-07-17 21:56:15 +02:00
FROM kasproject/kas:latest
Add Dockerfile for Isar image builder Isar requires a number of extra packages compared to a Yocto build. It also needs a newer e2fsprogs version which can be taken from backports. Last but not least, its keystone multistrap contains a nasty bug [1] under in jessie so that we need to pull the updated version from stretch. The value of having this image still based on jessie is that it can be used for both purposes: Yocto (2.1/2.2) and Isar builds. We push it along the kas core image as kas-isar during the CI run. Isar still requires some raised privileges. Therefore, the image has to be started with the additional switches "--cap-add=SYS_ADMIN --cap-add=MKNOD --device $(/sbin/losetup -f)". [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774698 Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-28 19:25:58 +02:00
ENV LC_ALL=en_US.UTF-8
Docker: move on to buster buster is the new stable, use it Signed-off-by: Henning Schild <henning.schild@siemens.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2019-07-31 12:25:03 +02:00
RUN apt-get update && \
Docker: Update to Debian stretch Time to move forward, buster is almost in sight. We may break some older Yocto versions this way, but they can always use older images. Along this update, this migrates the locale setup towards the recommendation on https://docs.docker.com/samples/library/debian/#locales. Furthermore, DEBIAN_FRONTEND=noninteractive is moved to the top-level Dockerfile - it's generic. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2018-07-17 21:56:15 +02:00
apt-get install -y -f --no-install-recommends \
Add Dockerfile for Isar image builder Isar requires a number of extra packages compared to a Yocto build. It also needs a newer e2fsprogs version which can be taken from backports. Last but not least, its keystone multistrap contains a nasty bug [1] under in jessie so that we need to pull the updated version from stretch. The value of having this image still based on jessie is that it can be used for both purposes: Yocto (2.1/2.2) and Isar builds. We push it along the kas core image as kas-isar during the CI run. Isar still requires some raised privileges. Therefore, the image has to be started with the additional switches "--cap-add=SYS_ADMIN --cap-add=MKNOD --device $(/sbin/losetup -f)". [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774698 Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-28 19:25:58 +02:00
autoconf automake gdisk libtool bash-completion \
docker: Take qemu-user-static from stretch for Isar image The jessie version easily crashes, e.g. during kernel build over dpkg-deb. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2018-02-27 07:57:08 +01:00
sudo grub2 grub-efi-amd64-bin grub-efi-ia32-bin \
Docker: Update to Debian stretch Time to move forward, buster is almost in sight. We may break some older Yocto versions this way, but they can always use older images. Along this update, this migrates the locale setup towards the recommendation on https://docs.docker.com/samples/library/debian/#locales. Furthermore, DEBIAN_FRONTEND=noninteractive is moved to the top-level Dockerfile - it's generic. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2018-07-17 21:56:15 +02:00
reprepro python3 binfmt-support e2fsprogs \
docker: Take debootstrap from stretch for Isar image The jessie version has a bug which prevents it from building debian "buster" and above. Signed-off-by: Henning Schild <henning.schild@siemens.com>
2018-04-18 15:36:38 +02:00
multistrap qemu-user-static debootstrap && \
Add Dockerfile for Isar image builder Isar requires a number of extra packages compared to a Yocto build. It also needs a newer e2fsprogs version which can be taken from backports. Last but not least, its keystone multistrap contains a nasty bug [1] under in jessie so that we need to pull the updated version from stretch. The value of having this image still based on jessie is that it can be used for both purposes: Yocto (2.1/2.2) and Isar builds. We push it along the kas core image as kas-isar during the CI run. Isar still requires some raised privileges. Therefore, the image has to be started with the additional switches "--cap-add=SYS_ADMIN --cap-add=MKNOD --device $(/sbin/losetup -f)". [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774698 Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-06-28 19:25:58 +02:00
apt-get clean && \
rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp*
RUN echo "builder ALL=NOPASSWD: ALL" > /etc/sudoers.d/builder-nopasswd && \
chmod 660 /etc/sudoers.d/builder-nopasswd
docker: Add binfmt-support for Isar cross-building Additionally requires to run the container with --privileged - not nice but unavoidable right now, see also https://groups.google.com/forum/#!topic/isar-users/Un75m49InjY Also note that running containers with different binfmt settings concurrently will cause troubles. Same for the case that the host requires deviating settings. Use carefully. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2017-09-05 10:58:52 +02:00
docker: isar: configure sudo to keep proxy env variables Keep proxy related env variables when running commands with sudo. Signed-off-by: Henning Schild <henning.schild@siemens.com>
2017-11-02 14:11:58 +01:00
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
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>
2019-03-19 15:25:02 +01:00
RUN sed -i 's|#!/bin/bash|\0\n\ndpkg-reconfigure qemu-user-static 2>\&1 \| grep -v "already enabled in kernel"|' /kas/docker-entrypoint
Reference in New Issue Copy Permalink