Dockerfile and Base Image¶
The core idea behind python helium is to be as lightweight as possible,
so this is based on the lightweight
Docker and Docker Compose¶
The Dockerfile extends
and installs twisted into the container on first run.
This can be used standalone by building using
However, the preferred way to use this image is to use the docker-compose file:
docker-compose build docker-compose up -d docker-compose down
This requires the container to listen for requests on multiple ports. The container should be bound to the correct address.
If Python Helium is listening for requests from an nginx container in the same pod, you can listen for any incoming request (no need to bind to a particular address). In this case the container will not have any external interface.
If Python Helium is listening for requests over a VPN, the service should be bound to the VPN IP address of the machine. This will ensure that the server only responds to (encrypted) requests from machines on the VPN.
Volumes and Bind Mounting¶
The Dockerfile expects the application to be at:
so bind mount the
helium.py application to
when you run this container.