From a1326dc31fde3d02efe37627c8edb3e0be5b28fe Mon Sep 17 00:00:00 2001
From: Christoph Wickert <christoph.wickert@suse.com>
Date: Fri, 13 Sep 2024 12:00:18 +0200
Subject: [PATCH] Modules -> Containers: Remove mention of docker-stable
 package (BSC#1230284)

This is a temporary fix until the package is released.

FIXME: Revert this commit once the package arrives and close JSC#PED-10699
---
 xml/art_modules.xml | 22 ----------------------
 1 file changed, 22 deletions(-)

diff --git a/xml/art_modules.xml b/xml/art_modules.xml
index 5957fa49a4..b204908586 100644
--- a/xml/art_modules.xml
+++ b/xml/art_modules.xml
@@ -278,28 +278,6 @@
                 Contains packages revolving around containers, including container engine and core
                 container-related tools like on-premise registry.
               </para>
-              <note>
-                <title><package>docker-stable</package></title>
-                <para>
-                  &suse; ships a package named <package>docker-stable</package>, based on selected versions
-                  of the the Moby project, which is the upstream for <phrase
-                    role="productname">&docker;</phrase>. When this version is no longer supported by the Moby
-                  project, &suse; will provide reactive support for an additional 3 years, which may require
-                  a LTSS subscription depending on the lifecycle of the underlying product.
-                </para>
-              </note>
-              <warning>
-                <title>Migration from <package>docker</package> to <package>docker-stable</package></title>
-                <para>
-                  In alignment with Moby project practices, &suse; neither tests nor supports downgrading
-                  <package>docker</package> to older versions. This policy is particularly relevant when
-                  considering a migration from the latest <package>docker</package> package to the
-                  <package>docker-stable</package> package, which in most cases would be an older version.
-                  Such a downgrade can result in unexpected side effects, compatibility issues and even
-                  disruptions to container production environments, and is not recommended for production
-                  systems.
-                </para>
-              </warning>
               <important>
                 <title>&docker; Swarm is not supported</title>
                 <para>