Skip to content

Commit e6d7cb4

Browse files
author
Brice Fallon-Freeman
authored
Merge pull request openshift#8118 from bfallonf/rpm_containerized
Updates to rpm vs containerized topic
2 parents 961f52b + 5eaf257 commit e6d7cb4

File tree

1 file changed

+18
-13
lines changed

1 file changed

+18
-13
lines changed

install_config/install/rpm_vs_containerized.adoc

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -13,29 +13,34 @@ toc::[]
1313

1414
== RPM vs Containerized Installation
1515

16-
An RPM installation installs all services through package management and
17-
configures services to run within the same user space, while a containerized
18-
installation installs services using container images and runs separate services
19-
in individual containers.
16+
You can opt to install {product-title} using the RPM or containerized package
17+
method. Either installation method results in a working environment, but the
18+
choice comes from the operating system and how you choose to update your hosts.
2019

20+
[IMPORTANT]
21+
====
2122
The default method for installing {product-title} on
2223
ifdef::openshift-origin[]
2324
Fedora, CentOS, or RHEL
2425
endif::[]
2526
ifdef::openshift-enterprise[]
2627
Red Hat Enterprise Linux (RHEL)
2728
endif::[]
28-
uses RPMs.
29-
30-
[IMPORTANT]
31-
====
32-
When targeting a Red Hat Atomic Host system, the containerized method is the
33-
only available option, and is automatically selected for you based on the
34-
detection of the *_/run/ostree-booted_* file.
29+
uses RPMs. When targeting a Red Hat Atomic Host system, the
30+
containerized method is the only available option, and is automatically selected
31+
for you based on the detection of the *_/run/ostree-booted_* file.
3532
====
3633

37-
The following table outlines the differences between the RPM and Containerized
38-
methods:
34+
When using RPMs, all services are installed and updated via package management
35+
from an outside source. These modify a host's existing configuration within the
36+
same user space. Alternatively, containerized installs instead are a complete,
37+
all-in-one resource using container images and its own operating system within
38+
the container. Any updated, newer containers replace any existing ones on your
39+
host. Choosing one method over the other depends on how you choose to update
40+
{product-title} in the future.
41+
42+
The following table outlines further differences between the RPM and
43+
Containerized methods:
3944

4045
[cols="h,2*",options="header"]
4146
|===

0 commit comments

Comments
 (0)