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

20 lines
654 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
ci: Push directly from build step Refactor the workflows so that we can use build-push-action also for publishing. This is a precondition for switching to buildx, needed for multi-arch images. The trick needed for this is using an environment variable to control whether we should push when building the master branch, initializing it according to the tag status. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-01-02 18:50:34 +01:00
ARG KAS_TAG=latest
FROM ghcr.io/siemens/kas/kas:$KAS_TAG
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: base containers on bullseye Currently the containers are based on buster, but use buster-backports, and (in case if the Isar container) even plain bullseye with pinning as additional deb soure. This changes that to use bullseye only. Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-11-17 07:25:02 +01: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 \
Dockerfile: move sudo to standard Dockerfile To expand the usability of the standard Docker image, move sudo enablement from Docker.isar. Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-04-26 17:01:59 +02:00
reprepro python3 binfmt-support e2fsprogs \
Add skopeo and umoci to ISAR image Skopeo and Umoci are needed for the new ISAR SDK Container target. A "manual" backport of Skopeo (and only Skopeo) is needed, since the repository "buster-backports" doesn't provide it. Signed-off-by: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com> [Jan: add golang-github-containers-{image,common} to buster list] Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-04-06 07:39:34 +02:00
umoci skopeo \
Dockerfile: base containers on bullseye Currently the containers are based on buster, but use buster-backports, and (in case if the Isar container) even plain bullseye with pinning as additional deb soure. This changes that to use bullseye only. Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
2021-11-17 07:25:02 +01: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
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