Skip to content

Commit aeceae4

Browse files
DOC-4096 (#160)
Added instructions to configure docker when not connected to the internet.
1 parent 4375679 commit aeceae4

File tree

1 file changed

+22
-2
lines changed

1 file changed

+22
-2
lines changed

docs-src/zdm-core/modules/migrate/pages/setup-ansible-playbooks.adoc

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,34 @@ image::{imagesprefix}docker-container-and-zdm-utility.png[ZDM Proxy connections
2323
. Docker needs to be installed on the machine that will be running the Ansible Control Host container. For comprehensive installation instructions, please refer to the https://docs.docker.com/engine/install/#server[official Docker documentation].
2424
. The `docker` command must not require superuser privileges. The instructions to do this can be found https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user[here].
2525

26-
That's it!
27-
2826
[NOTE]
2927
====
3028
Please note that the manual, non-superuser installation of Docker described above is to be done on the machine that will run the Ansible Control Host.
3129
From that point, the automation will take care of installing Docker on the ZDM Proxy machines without further intervention.
3230
====
3331

32+
== Alternative Docker configurations
33+
34+
There are two options for users who don't want to pull from a specific registry or are not connecting servers directly to the internet.
35+
36+
Option 1: Pull through local cache::
37+
Servers can connect directly to the Docker local registry so that the server then pulls containers from the internet itself.
38+
See the https://docs.docker.com/docker-hub/mirror/[Docker documentation] for instructions on how to set up a pull through cache.
39+
This option makes it possible to only have the local Docker registry connected to the internet.
40+
41+
Option 2: Unconnected local registry::
42+
Local registries not connected to the internet require administrators to manually add containers to their registry.
43+
For {zdm-utility} users, this option requires the following five containers to install and configure the jumphost, ZDM Proxy, and monitoring:
44+
45+
[source,no-highlight]
46+
----
47+
grafana/grafana:7.5.17
48+
prom/prometheus:latest
49+
datastax/zdm-ansible:2.x
50+
prom/node-exporter:latest
51+
datastax/zdm-proxy:2.x
52+
----
53+
3454
== Jumphost
3555

3656
In this guide, we'll use a jumphost to run the Ansible Control Host container.

0 commit comments

Comments
 (0)