[PATCH] automation: Drop sles11sp4 dockerfile

[PATCH] automation: Drop sles11sp4 dockerfile

[Michal Orzel]

It has reached EOL and there are no jobs using it on any branch.

Signed-off-by: Michal Orzel <michal.orzel@amd.com>
---
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="xen-devel@lists.xenproject.org"
-
-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

Re: [PATCH] automation: Drop sles11sp4 dockerfile

[Andrew Cooper]

On 03/03/2023 12:53 pm, Michal Orzel wrote:
> It has reached EOL and there are no jobs using it on any branch.
>
> Signed-off-by: Michal Orzel <michal.orzel@amd.com>

Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>

I'll drop the registry tags when I commit this.

Re: [PATCH] automation: Drop sles11sp4 dockerfile

[Stefano Stabellini]

On Fri, 3 Mar 2023, Michal Orzel wrote:
> It has reached EOL and there are no jobs using it on any branch.
> 
> Signed-off-by: Michal Orzel <michal.orzel@amd.com>

Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>


> ---
> 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="xen-devel@lists.xenproject.org"
> -
> -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
>