-
Notifications
You must be signed in to change notification settings - Fork 4
Introduction
- As a user, I want to start the containers without needing docker volumes, or any external data, so I can test the docker images as they are.*
- As a user, I want to run the webui container and the worker container on different machines without needing docker volumes, or any external data, so I can test the docker images as they are.*
- As a user, I want that the containers provide hints for text files configuration, to allow me know which parameters are available to configure the services inside the container.
- As a user, I want to be able to use volumes to keep important data outside the container on productive instances.
- For 1 and 2, the parameter --link is not considered external data, even when an external ip address is provided.
There are two Dockerfiles included in this project. Each Dockerfile has a version label which contains the date last modified. This helps to know which Dockerfile version was used to build each docker image.
The generated images can be found on docker hub here: https://hub.docker.com/u/binarysequence/
- docker image for webui: https://hub.docker.com/r/binarysequence/openqa-webui/
- docker image for worker-x86_64: https://hub.docker.com/r/binarysequence/openqa-worker-x86_64/
Each docker image is also tagged with a build date. This helps to find the Dockerfile version used. But they may not have the same date, since the same Dockerfile can be reused to build an image with a more recent openQA version and a more recent Tumbleweed snapshot.
If an image has the tag 2017-11-24, the Dockerfile used may have version 2017-11-24 or less (like 2017-11-22).
Git tags are used to mark the commit that contains the Dockerfile version. For example, the commit tagged with webui_2017-11-15 contains the Dockerfile used as version 2017-11-15.