Skip to content

Commit f89623c

Browse files
anarnold97anarnold97
authored
Merge pull request #888 from anarnold97/mta-7-0-3-release-notes-quick-fix
Update
2 parents 901b27c + 2ae148d commit f89623c

File tree

5 files changed

+138
-4
lines changed

5 files changed

+138
-4
lines changed

‎docs/release-notes/master.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ include::topics/making-open-source-more-inclusive.adoc[]
2222

2323
include::topics/mta-rn-known-issues-7-0-3.adoc[leveloffset=+2]
2424

25-
include::topics/cli-tool-known-issues.adoc[leveloffset=+3]
25+
include::topics/cli-tool-known-issues-703.adoc[leveloffset=+3]
2626

2727
include::topics/mta-rn-resolved-issues-7-0-3.adoc[leveloffset=+2]
2828

@@ -34,7 +34,7 @@ include::topics/mta-rn-new-features-7-0-2.adoc[leveloffset=+2]
3434

3535
include::topics/mta-rn-known-issues-7-0-2.adoc[leveloffset=+2]
3636

37-
include::topics/cli-tool-known-issues.adoc[leveloffset=+3]
37+
include::topics/cli-tool-known-issues-702.adoc[leveloffset=+3]
3838

3939
include::topics/mta-rn-resolved-issues-7-0-2.adoc[leveloffset=+2]
4040

@@ -46,7 +46,7 @@ include::topics/mta-rn-upgrade-notes-7-0-2.adoc[leveloffset=+2]
4646

4747
include::topics/mta-rn-known-issues-7-0-1.adoc[leveloffset=+2]
4848

49-
include::topics/cli-tool-known-issues.adoc[leveloffset=+3]
49+
include::topics/cli-tool-known-issues-701.adoc[leveloffset=+3]
5050

5151
include::topics/mta-rn-resolved-issues-7-0-1.adoc[leveloffset=+2]
5252

‎docs/topics/cli-tool-known-issues-701.adoc‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/cli-guide/master.adoc
4+
5+
:_content-type: PROCEDURE
6+
7+
[id="cli-tool-known-issues-701_{context}"]
8+
= {CLINameTitle} known issues
9+
10+
.Limitations with Podman on Microsoft Windows
11+
12+
The {CLINameTitle} is built and distributed with support for Microsoft Windows.
13+
14+
However, when running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error can be returned when starting the container:
15+
16+
[source,terminal]
17+
----
18+
Fatal glibc error: CPU does not support x86-64-v2
19+
----
20+
21+
This error is caused because Red Hat Enterprise Linux 9 or Universal Base Image 9 container images must be run on a CPU architecture that supports `x86-64-v2`.
22+
23+
For more details, see link:https://access.redhat.com/solutions/7057314[(Running Red Hat Enterprise Linux 9 (RHEL) or Universal Base Image (UBI) 9 container images fail with "Fatal glibc error: CPU does not support x86-64-v2")].
24+
25+
{CLINameTitle} runs the container runtime correctly. However, different container runtime configurations are not supported.
26+
27+
Although unsupported, you can run {CLINameTitle} with *Docker* instead of *Podman*, which would resolve this issue.
28+
29+
To achieve this, you replace the `PODMAN_BIN` path with the path to Docker.
30+
31+
For example, if you experience this issue, instead of issuing:
32+
33+
[source,terminal]
34+
----
35+
PODMAN_BIN=/usr/local/bin/docker mta-cli analyze
36+
----
37+
38+
You replace `PODMAN_BIN` with the path to Docker:
39+
40+
[source,terminal]
41+
----
42+
<Docker Root Dir>=/usr/local/bin/docker mta-cli analyze
43+
----
44+
45+
While this is not supported, it would allow you to explore {CLINameTitle} while you work to upgrade your hardware or move to hardware that supports `x86_64-v2`.

‎docs/topics/cli-tool-known-issues-702.adoc‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/cli-guide/master.adoc
4+
5+
:_content-type: PROCEDURE
6+
7+
[id="cli-tool-known-issues-702_{context}"]
8+
= {CLINameTitle} known issues
9+
10+
.Limitations with Podman on Microsoft Windows
11+
12+
The {CLINameTitle} is built and distributed with support for Microsoft Windows.
13+
14+
However, when running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error can be returned when starting the container:
15+
16+
[source,terminal]
17+
----
18+
Fatal glibc error: CPU does not support x86-64-v2
19+
----
20+
21+
This error is caused because Red Hat Enterprise Linux 9 or Universal Base Image 9 container images must be run on a CPU architecture that supports `x86-64-v2`.
22+
23+
For more details, see link:https://access.redhat.com/solutions/7057314[(Running Red Hat Enterprise Linux 9 (RHEL) or Universal Base Image (UBI) 9 container images fail with "Fatal glibc error: CPU does not support x86-64-v2")].
24+
25+
{CLINameTitle} runs the container runtime correctly. However, different container runtime configurations are not supported.
26+
27+
Although unsupported, you can run {CLINameTitle} with *Docker* instead of *Podman*, which would resolve this issue.
28+
29+
To achieve this, you replace the `PODMAN_BIN` path with the path to Docker.
30+
31+
For example, if you experience this issue, instead of issuing:
32+
33+
[source,terminal]
34+
----
35+
PODMAN_BIN=/usr/local/bin/docker mta-cli analyze
36+
----
37+
38+
You replace `PODMAN_BIN` with the path to Docker:
39+
40+
[source,terminal]
41+
----
42+
<Docker Root Dir>=/usr/local/bin/docker mta-cli analyze
43+
----
44+
45+
While this is not supported, it would allow you to explore {CLINameTitle} while you work to upgrade your hardware or move to hardware that supports `x86_64-v2`.

‎docs/topics/cli-tool-known-issues-703.adoc‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * docs/cli-guide/master.adoc
4+
5+
:_content-type: PROCEDURE
6+
7+
[id="cli-tool-known-issues-703_{context}"]
8+
= {CLINameTitle} known issues
9+
10+
.Limitations with Podman on Microsoft Windows
11+
12+
The {CLINameTitle} is built and distributed with support for Microsoft Windows.
13+
14+
However, when running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error can be returned when starting the container:
15+
16+
[source,terminal]
17+
----
18+
Fatal glibc error: CPU does not support x86-64-v2
19+
----
20+
21+
This error is caused because Red Hat Enterprise Linux 9 or Universal Base Image 9 container images must be run on a CPU architecture that supports `x86-64-v2`.
22+
23+
For more details, see link:https://access.redhat.com/solutions/7057314[(Running Red Hat Enterprise Linux 9 (RHEL) or Universal Base Image (UBI) 9 container images fail with "Fatal glibc error: CPU does not support x86-64-v2")].
24+
25+
{CLINameTitle} runs the container runtime correctly. However, different container runtime configurations are not supported.
26+
27+
Although unsupported, you can run {CLINameTitle} with *Docker* instead of *Podman*, which would resolve this issue.
28+
29+
To achieve this, you replace the `PODMAN_BIN` path with the path to Docker.
30+
31+
For example, if you experience this issue, instead of issuing:
32+
33+
[source,terminal]
34+
----
35+
PODMAN_BIN=/usr/local/bin/docker mta-cli analyze
36+
----
37+
38+
You replace `PODMAN_BIN` with the path to Docker:
39+
40+
[source,terminal]
41+
----
42+
<Docker Root Dir>=/usr/local/bin/docker mta-cli analyze
43+
----
44+
45+
While this is not supported, it would allow you to explore {CLINameTitle} while you work to upgrade your hardware or move to hardware that supports `x86_64-v2`.

‎docs/topics/cli-tool-known-issues.adoc‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@
1111

1212
The {CLINameTitle} is built and distributed with support for Microsoft Windows.
1313

14-
1514
However, when running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error can be returned when starting the container:
1615

1716
[source,terminal]

0 commit comments

Comments
 (0)