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

25 lines
1.2 KiB
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
Switch to github workflow Add the github/ghcr equivalent to travis/dockerhub. With this in place, we can also deploy the next and latest images to ghcr. Adjust Dockerfile.isar accordingly. Also update the badge shown in the README. We model the workflow with github a bit differently than so far: next and master branch are different workflows. The former includes testing, the latter just updates the container image. This is based on the (offline) workflow to push changes to next first and have no commits in master that haven't been in next before, except for release commits. The master workflow also triggers on tags in which case it additionally tags the container images accordingly and pushed that as well. Travis is removed in the same run to avoid pushing differently built images to the different registries. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2020-09-23 11:36:12 +02:00
FROM ghcr.io/siemens/kas/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
Dockerfile: Make DEBIAN_FRONTEND non-persistent Only use this setting during non-interactive build, not in the possibly interactive image. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-01-02 15:48:05 +01:00
ARG DEBIAN_FRONTEND=noninteractive
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
Dockerfile.isar: Pull qemu-user-static from buster-backports 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>
2020-09-23 09:15:16 +02:00
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 && \
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 \
Dockerfile.isar: Drop grub package The leakage of grub artifacts from the building Debian version and the usage its grub tools was fixed in Isar 0.6 already. No one is expected to use that old version with latest kas containers, and the presence of these packages also collide with providing non-x86 versions. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-01-03 18:36:38 +01:00
sudo reprepro python3 binfmt-support e2fsprogs \
Docker: Add quilt to kas-isar Will become a hard dependency when switching the (currently broken) patch class of Isar to one derived from OE. Prepare for that. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2019-08-13 18:39:11 +02:00
multistrap qemu-user-static debootstrap quilt && \
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 && \
Dockerfile.isar: preserve /var/tmp directory from an unwanted removal Fix a bug in the Docker image build process that delete /var/tmp directory. Desired is only delete its content. Signed-off-by: Matteo Facchinetti <matteo.facchinetti@sirius-es.it> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2019-08-29 17:34:12 +02:00
rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
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
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: Escape special characters Escape '&' '\&' as sed replace & with the search term. Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2020-11-23 16:00:19 +01:00
RUN sed -i 's|#!/bin/bash|\0\n\nupdate-binfmts --enable \&\& [ -f /proc/sys/fs/binfmt_misc/status ]|' /kas/container-entrypoint
Reference in New Issue Copy Permalink