diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md index 3712de130a..ac762920f1 100644 --- a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md +++ b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md @@ -100,30 +100,26 @@ Make sure to use a supported combination of Linux distribution and container eng * For Podman 5 - * Install version `5.2.2-13.*` using dnf. + * Install the latest available version of Podman `5.2.2` using dnf. :::{note} - As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-13` since this is the latest supported version. - - If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-13` with the desired version in the commands below. - - The version lock is still required for previous versions, to prevent automatic in-place updates that may be affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). + 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. ::: ```sh - sudo dnf install podman-5.2.2-13.* podman-remote-5.2.2-13.* + sudo dnf install podman-5.2.2 podman-remote-5.2.2 ``` - * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-13.*`. + * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`. ```sh ## Install versionlock sudo dnf install 'dnf-command(versionlock)' ## Lock major version - sudo dnf versionlock add --raw 'podman-5.2.2-13.*' - sudo dnf versionlock add --raw 'podman-remote-5.2.2-13.*' + sudo dnf versionlock add --raw 'podman-5.2.2' + sudo dnf versionlock add --raw 'podman-remote-5.2.2' - ## Verify that podman-5.2.2-13.* and podman-remote-5.2.2-13.* appear in the output + ## Verify that podman-5.2.2 and podman-remote-5.2.2 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 3c3aa78d55..d4d8dff78c 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,30 +129,27 @@ Using Docker or Podman as container runtime is a configuration local to the host * For Podman 5 - * Install version `5.2.2-13.*` using dnf. + * Install the latest available version of Podman `5.2.2` using dnf. :::{note} - As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-13` since this is the latest supported version. - - If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-13` with the desired version in the commands below. - - The version lock is still required for previous versions, to prevent automatic in-place updates that may be affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). + 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. ::: ```sh - sudo dnf install podman-5.2.2-13.* podman-remote-5.2.2-13.* + sudo dnf install podman-5.2.2 podman-remote-5.2.2 ``` - * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-13.*`. + + * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`. ```sh ## Install versionlock sudo dnf install 'dnf-command(versionlock)' ## Lock major version - sudo dnf versionlock add --raw 'podman-5.2.2-13.*' - sudo dnf versionlock add --raw 'podman-remote-5.2.2-13.*' + sudo dnf versionlock add --raw 'podman-5.2.2' + sudo dnf versionlock add --raw 'podman-remote-5.2.2' - ## Verify that podman-5.2.2-13.* and podman-remote-5.2.2-13.* appear in the output + ## Verify that podman-5.2.2 and podman-remote-5.2.2 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 1eb8a3364a..bb661ecace 100644 --- a/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md +++ b/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md @@ -5,36 +5,27 @@ applies_to: --- # Migrating to Podman 5 -Following are the supported upgrade paths for Podman 5 in {{ece}}. +This guide describes the supported ways to upgrade or migrate your {{ece}} (ECE) hosts to Podman 5. There are two primary methods: -| **From ↓** ... **To →** | Podman 5.2.2-9 | Podman 5.2.2-11 | Podman 5.2.2-13 | 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 | X | X | -| **Podman 5.2.2-9 (in-place)** | - | X | X | X | +* **In-place upgrade**: Update Podman directly on existing ECE hosts without replacing them. In-place upgrades to Podman 5 are only supported from existing Podman-based hosts. +* **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. +:::{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. +::: -^*^ *Supported but not recommended given that a newer version (Podman `5.2.2-13`) is available.* +The following table summarizes the supported upgrade paths to Podman 5 in ECE. -Podman `5.2.2-13` is only supported when conducting a **fresh {{ece}} installation** or performing a **grow-and-shrink update** from Docker or Podman 4. +| **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 | -For **in-place updates**, it is recommended to use Podman `5.2.2-9`, since upgrades to 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). -When performing an in-place update, make sure to configure the Podman version to be locked at version `5.2.2-9.*`, by following the instructions below. - -```sh -## Install versionlock -sudo dnf install 'dnf-command(versionlock)' - -## Lock major version -sudo dnf versionlock add --raw 'podman-5.2.2-9.*' -sudo dnf versionlock add --raw 'podman-remote-5.2.2-9.*' - -## Verify that podman-5.2.2-9.* and podman-remote-5.2.2-9.* appear in the output -sudo dnf versionlock list -``` - -Podman versions `5.2.3` and higher are not supported. \ No newline at end of file +As shown in the table above, [migrations from Docker](./migrate-ece-to-podman-hosts.md) are only supported using the grow-and-shrink method.