diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md index fc9d83daf3..1a89f797c4 100644 --- a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md +++ b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md @@ -100,26 +100,26 @@ Make sure to use a supported combination of Linux distribution and container eng * For Podman 5 - * Install the latest available version of Podman `5.2.2` using dnf. + * Install the latest available version `5.*` using dnf. :::{note} - Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later build of `5.2.2`, such as `5.2.2-16` or newer. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information. + Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later version. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information. ::: ```sh - sudo dnf install podman-5.2.2 podman-remote-5.2.2 + sudo dnf install podman-5.* podman-remote-5.* ``` - * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`. + * To prevent automatic Podman major version updates, configure the Podman version to be locked at version `5.*` while still allowing minor and patch updates. ```sh ## Install versionlock sudo dnf install 'dnf-command(versionlock)' ## Lock major version - sudo dnf versionlock add --raw 'podman-5.2.2' - sudo dnf versionlock add --raw 'podman-remote-5.2.2' + sudo dnf versionlock add --raw 'podman-5.*' + sudo dnf versionlock add --raw 'podman-remote-5.*' - ## Verify that podman-5.2.2 and podman-remote-5.2.2 appear in the output + ## Verify that podman-5.* and podman-remote-5.* appear in the output sudo dnf versionlock list ``` diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md index 1cee5751a0..b4ab3000aa 100644 --- a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md +++ b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md @@ -129,27 +129,27 @@ Using Docker or Podman as container runtime is a configuration local to the host * For Podman 5 - * Install the latest available version of Podman `5.2.2` using dnf. + * Install the latest available version `5.*` using dnf. :::{note} - Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later build of `5.2.2`, such as `5.2.2-16` or newer. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information. + Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later version. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information. ::: ```sh - sudo dnf install podman-5.2.2 podman-remote-5.2.2 + sudo dnf install podman-5.* podman-remote-5.* ``` - * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`. + * To prevent automatic Podman major version updates, configure the Podman version to be locked at version `5.*` while still allowing minor and patch updates. ```sh ## Install versionlock sudo dnf install 'dnf-command(versionlock)' ## Lock major version - sudo dnf versionlock add --raw 'podman-5.2.2' - sudo dnf versionlock add --raw 'podman-remote-5.2.2' + sudo dnf versionlock add --raw 'podman-5.*' + sudo dnf versionlock add --raw 'podman-remote-5.*' - ## Verify that podman-5.2.2 and podman-remote-5.2.2 appear in the output + ## Verify that podman-5.* and podman-remote-5.* appear in the output sudo dnf versionlock list ``` diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md b/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md index f414b1af51..8424603440 100644 --- a/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md +++ b/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md @@ -13,21 +13,21 @@ This guide describes the supported ways to upgrade or migrate your {{ece}} (ECE) * **Grow-and-shrink upgrade**: [Add new hosts](./install-ece-on-additional-hosts.md) running the desired Podman version to your ECE installation, then [remove the old ones](/deploy-manage/uninstall/uninstall-elastic-cloud-enterprise.md). This method is safer and preferred, as it avoids potential risks associated with upgrading the container engine or the operating system in place. -ECE only supports Podman 5 in version `5.2.2`, regardless of your upgrade method. Later versions such as `5.2.3` and above are not supported. Refer always to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for details on supported versions. +ECE supports Podman 5, regardless of your upgrade method. Refer always to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for details on supported versions. :::{important} -Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this issue, use a later build such as `5.2.2-16` or newer. +Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this issue, use a later podman version. ::: The following table summarizes the supported upgrade paths to Podman 5 in ECE. -| **From ↓** ... **To →** | Podman 5.2.2-latest | Podman 5.2.3 | -|-----------------------------------------|-----------------|--------------| -| ** (grow)** | ✓ | X | -| **Docker (grow-and-shrink)** | ✓ | X | -| **Podman 4.9.4 (grow-and-shrink)** | ✓ | X | -| **Podman 4.9.4 (in-place)** | ✓ | X | -| **Podman 5.2.2 (grow-and-shrink)** | ✓ | X | -| **Podman 5.2.2 (in-place)** | ✓ | X | +| **From ↓** ... **To →** | Podman 5 | +|-----------------------------------------|-----------------| +| ** (grow)** | ✓ | +| **Docker (grow-and-shrink)** | ✓ | +| **Podman 4.9.4 (grow-and-shrink)** | ✓ | +| **Podman 4.9.4 (in-place)** | ✓ | +| **Podman 5.2.2 (grow-and-shrink)** | ✓ | +| **Podman 5.2.2 (in-place)** | ✓ | As shown in the table above, [migrations from Docker](./migrate-ece-to-podman-hosts.md) are only supported using the grow-and-shrink method.