blob: 50593af6e95369113e842d0e2a02260930060186 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
#!/bin/bash -e
cat <<"EOF"
The ose-ansible image provides several options to control the behaviour of the containers.
For more details on these options see the documentation:
https://github.com/openshift/openshift-ansible/blob/master/README_CONTAINER_IMAGE.md
At a minimum, when running a container using this image you must provide:
* ssh keys so that Ansible can reach your hosts. These should be mounted as a volume under
/opt/app-root/src/.ssh
* An inventory file. This can be mounted inside the container as a volume and specified with the
INVENTORY_FILE environment variable. Alternatively you can serve the inventory file from a web
server and use the INVENTORY_URL environment variable to fetch it.
* The playbook to run. This is set using the PLAYBOOK_FILE environment variable.
Here is an example of how to run a containerized ose-ansible with
the openshift_facts playbook, which collects and displays facts about your
OpenShift environment. The inventory and ssh keys are mounted as volumes
(the latter requires setting the uid in the container and SELinux label
in the key file via :Z so they can be accessed) and the PLAYBOOK_FILE
environment variable is set to point to the playbook within the image:
docker run -tu `id -u` \
-v $HOME/.ssh/id_rsa:/opt/app-root/src/.ssh/id_rsa:Z,ro \
-v /etc/ansible/hosts:/tmp/inventory:Z,ro \
-e INVENTORY_FILE=/tmp/inventory \
-e OPTS="-v" \
-e PLAYBOOK_FILE=playbooks/byo/openshift_facts.yml \
openshift3/ose-ansible
EOF
|
