Skip to content

Commit d29ebea

Browse files
committed
update to reflect the sync result with ECE dev
1 parent de257ba commit d29ebea

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -100,26 +100,26 @@ Make sure to use a supported combination of Linux distribution and container eng
100100

101101
* For Podman 5
102102

103-
* Install the latest available version of Podman `5.4` using dnf.
103+
* Install the latest available version `5.*` using dnf.
104104

105105
:::{note}
106106
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.
107107
:::
108108

109109
```sh
110-
sudo dnf install podman-5.4.* podman-remote-5.4.*
110+
sudo dnf install podman-5.* podman-remote-5.*
111111
```
112-
* To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.4.*`.
112+
* To prevent automatic Podman major version updates, configure the Podman version to be locked at version `5.*` while still allowing minor and patch updates.
113113

114114
```sh
115115
## Install versionlock
116116
sudo dnf install 'dnf-command(versionlock)'
117117
118118
## Lock major version
119-
sudo dnf versionlock add --raw 'podman-5.4.*'
120-
sudo dnf versionlock add --raw 'podman-remote-5.4.*'
119+
sudo dnf versionlock add --raw 'podman-5.*'
120+
sudo dnf versionlock add --raw 'podman-remote-5.*'
121121
122-
## Verify that podman-5.4.* and podman-remote-5.4.* appear in the output
122+
## Verify that podman-5.* and podman-remote-5.* appear in the output
123123
sudo dnf versionlock list
124124
```
125125

deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -129,27 +129,27 @@ Using Docker or Podman as container runtime is a configuration local to the host
129129

130130
* For Podman 5
131131

132-
* Install the latest available version of Podman `5.4` using dnf.
132+
* Install the latest available version `5.*` using dnf.
133133

134134
:::{note}
135135
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.
136136
:::
137137

138138
```sh
139-
sudo dnf install podman-5.4.* podman-remote-5.4.*
139+
sudo dnf install podman-5.* podman-remote-5.*
140140
```
141141

142-
* To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.4.*`.
142+
* To prevent automatic Podman major version updates, configure the Podman version to be locked at version `5.*` while still allowing minor and patch updates.
143143

144144
```sh
145145
## Install versionlock
146146
sudo dnf install 'dnf-command(versionlock)'
147147
148148
## Lock major version
149-
sudo dnf versionlock add --raw 'podman-5.4.*'
150-
sudo dnf versionlock add --raw 'podman-remote-5.4.*'
149+
sudo dnf versionlock add --raw 'podman-5.*'
150+
sudo dnf versionlock add --raw 'podman-remote-5.*'
151151
152-
## Verify that podman-5.4.* and podman-remote-5.4.* appear in the output
152+
## Verify that podman-5.* and podman-remote-5.* appear in the output
153153
sudo dnf versionlock list
154154
```
155155

deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ This guide describes the supported ways to upgrade or migrate your {{ece}} (ECE)
1313

1414
* **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.
1515

16-
ECE supports Podman 5 in version `5.4`, 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.
16+
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.
1717

1818
:::{important}
1919
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.
2020
:::
2121

2222
The following table summarizes the supported upgrade paths to Podman 5 in ECE.
2323

24-
| **From ↓** ... **To →** | Podman 5.4 |
24+
| **From ↓** ... **To →** | Podman 5 |
2525
|-----------------------------------------|-----------------|
2626
| **<vanilla Linux installation> (grow)** ||
2727
| **Docker (grow-and-shrink)** ||

0 commit comments

Comments
 (0)