Fix pip install in unit test container

The SWIG_FEATURES environment variable is to get pip install working with M2Crypto==0.22.3. It works without SWIG_FEATURES if we update to M2Crypto >= 0.23.0.

Also did some organization, add README.

tools/docker-compose/unit-tests/Dockerfile

@@ -1,11 +1,6 @@
 # FROM gcr.io/ansible-tower-engineering/tower_devel:latest
 FROM centos
 
-# RUN locale-gen en_US.UTF-8
-# ENV LANG en_US.UTF-8
-# ENV LANGUAGE en_US:en
-# ENV LC_ALL en_US.UTF-8
-
 RUN yum install -y epel-release
 
 RUN yum install -y \
@@ -39,9 +34,7 @@ RUN yum install -y nodejs
 RUN npm set progress=false
 
 WORKDIR "/ansible-tower"
-ENV SHELL /bin/bash
-ENV PATH /usr/bin:$PATH
-ENV SWIG_FEATURES="-cpperraswarn -includeall -D__`uname -m`__ -I/usr/include/openssl"
+
 ENV VENV_BASE="/venv"
 ENTRYPOINT ["/bin/bash", "-c"]
-CMD ["make requirements_test test"]
+CMD ["bash"]

tools/docker-compose/unit-tests/README.md

@@ -0,0 +1,15 @@
+Run from the root of the repo:
+
+```shell
+$ docker-compose -f tools/docker-compose/unit-tests/docker-compose.yml run unit-tests
+```
+
+This will start the container, install the dependencies, and run the unit tests.
+
+If you just want to pop into a shell and poke around, run:
+
+```shell
+$ docker-compose -f tools/docker-compose/unit-tests/docker-compose.yml run unit-tests bash
+```
+
+If you run into any weirdness, it's probably a good idea to just give up and `make clean`.

tools/docker-compose/unit-tests/docker-compose.yml

@@ -0,0 +1,13 @@
+---
+version: '2'
+services:
+  unit-tests:
+    build:
+      context: ../../../
+      dockerfile: tools/docker-compose/unit-tests/Dockerfile
+    environment:
+      SWIG_FEATURES: "-cpperraswarn -includeall -I/usr/include/openssl"
+    command: ["make requirements_test test"]
+
+    volumes:
+      - ../../../:/ansible-tower