awx/tools/docker-isolated-override.yml

version: '3'
services:
  # Primary Tower Development Container link
  tower:
    environment:
      DOCKER_TOOLS_DIR: tools/docker-isolated
    links:
      - isolated
  # Isolated Rampart Container
  isolated:
    image: gcr.io/ansible-tower-engineering/tower_isolated:${TAG}
    hostname: isolated
    volumes:
      - "../awx/main/isolated:/tower_devel"
      - "../awx/lib:/tower_lib"
      - "/sys/fs/cgroup:/sys/fs/cgroup:ro"
    privileged: true
Support for executing job and adhoc commands on isolated Tower nodes (#6524) 2017-06-14 18:47:30 +03:00			`version: '3'`
			`services:`
			`# Primary Tower Development Container link`
			`tower:`
			`environment:`
			`DOCKER_TOOLS_DIR: tools/docker-isolated`
			`links:`
			`- isolated`
			`# Isolated Rampart Container`
			`isolated:`
			`image: gcr.io/ansible-tower-engineering/tower_isolated:${TAG}`
			`hostname: isolated`
			`volumes:`
Include the Tower venv in the isolated bubblewrapped arguments. This moves the container-based code location and venvs. The goal here is that the paths of Tower source for isolated vs normal nodes matches (both in prod and local development) so that we don't have to add a bunch of additional bwrap argument logic for <location-of-isolated-tower-venv>. 2017-06-19 18:15:16 +03:00			`- "../awx/main/isolated:/tower_devel"`
Support for executing job and adhoc commands on isolated Tower nodes (#6524) 2017-06-14 18:47:30 +03:00			`- "../awx/lib:/tower_lib"`
			`- "/sys/fs/cgroup:/sys/fs/cgroup:ro"`
			`privileged: true`