From 269192e8aa7f0ef85ca02326a5814fc161b1d6b1 Mon Sep 17 00:00:00 2001
From: kurokobo <2920259+kurokobo@users.noreply.github.com>
Date: Tue, 20 Jul 2021 10:53:45 -0400
Subject: [PATCH] fix: add guide for awx-ee

---
 runner/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/runner/README.md b/runner/README.md
index 7084f3c..8c15bfc 100644
--- a/runner/README.md
+++ b/runner/README.md
@@ -36,4 +36,5 @@ The settings can also be given directly as arguments like `--container-image` wi
 - If `process_isolation` is set to `false` as default, `ansible-runner` will just work as a wrapper for the local `ansible-playbook` command.
 - If `process_isolation` is set to `true`, `connection: local` points to the container itself, so the playbook cannot affect `localhost` which means the container host. To avoid this, you need to SSH to local host without using `connection: local`. [Related issues is here](https://github.com/ansible/ansible-runner/issues/752).
 - `container_image` defaults to `quay.io/ansible/ansible-runner:devel`. You can check available tags for the public Execution Environment at [`quay.io/ansible/ansible-runner`](https://quay.io/repository/ansible/ansible-runner?tab=tags)
+- The image from [`quay.io/ansible/awx-ee`](https://quay.io/repository/ansible/awx-ee?tab=tags) which is default Execution Environment for AWX also can be specified.
 - The `process_isolation_show_paths` described in the documentation does not work with Docker and Podman. Instead, you can use `container_volume_mounts` as described in [`env/settings`](env/settings), but this is not documented.