Skip to content

Commit

Permalink
Modules -> Containers: Clarify support and lifecycle (BSC#1230284)
Browse files Browse the repository at this point in the history
  • Loading branch information
cwickert committed Sep 12, 2024
1 parent 8a9f5c7 commit 61228a1
Showing 1 changed file with 31 additions and 1 deletion.
32 changes: 31 additions & 1 deletion xml/art_modules.xml
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,8 @@
</para>
</entry>
<entry>
<simplelist ><member><emphasis role="bold">Lifecycle:</emphasis> 10 yrs
<simplelist ><member><emphasis role="bold">Lifecycle:</emphasis> By package; follows
the upstream community of the respective package.
</member><member><emphasis role="bold">Extended:</emphasis> 3 yrs
LTSS<superscript>1</superscript></member><member><emphasis role="bold">Level:</emphasis> L3
</member>
Expand All @@ -277,6 +278,35 @@
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>
&suse; does not provide any support related to use of <phrase role="productname">&docker;
Swarm</phrase> orchestration. Related packages are shipped for customer convenience only.
</para>
</important>
</entry>
</row>
<row>
Expand Down

0 comments on commit 61228a1

Please sign in to comment.