It has reached EOL and there are no jobs using it on any branch. Signed-off-by: Michal Orzel <[email protected]> --- We can also safely remove sles containers from registry. --- automation/build/suse/sles11sp4.dockerfile | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 automation/build/suse/sles11sp4.dockerfile
diff --git a/automation/build/suse/sles11sp4.dockerfile b/automation/build/suse/sles11sp4.dockerfile deleted file mode 100644 index ff69a99afc71..000000000000 --- a/automation/build/suse/sles11sp4.dockerfile +++ /dev/null @@ -1,20 +0,0 @@ -FROM registry.gitlab.com/xen-project/xen/suse:sles11sp4-base -LABEL maintainer.name="The Xen Project" \ - maintainer.email="[email protected]" - -ENV USER root - -RUN mkdir /build -WORKDIR /build - -# Nothing else is needed -- base image already contain everything. - -# Note: -# -# SLES11 SP4 runs pre-2.13 glibc, which requires vsyscall support. Most -# distros nowadays disable vsyscall. To run this container, the host needs to -# have vsyscall=emulate in its kernel command line. -# -# Due to various issues in SLES11 SP4, you might want to disable building -# certain components. Known *not bulding* components include OVMF, SEABIOS -# and upstream QEMU. -- 2.25.1
