diff options
Diffstat (limited to 'BUILD.md')
| -rw-r--r-- | BUILD.md | 25 |
1 files changed, 17 insertions, 8 deletions
@@ -26,19 +26,28 @@ tito build --rpm ## Build an openshift-ansible container image +**NOTE**: the examples below use "openshift-ansible" as the name of the image to build for simplicity and illustration purposes, and also to prevent potential confusion between custom built images and official releases. See [README_CONTAINER_IMAGE.md](README_CONTAINER_IMAGE.md) for details about the released container images for openshift-ansible. + To build a container image of `openshift-ansible` using standalone **Docker**: cd openshift-ansible - docker build -t openshift/openshift-ansible . - -Alternatively this can be built using on **OpenShift** using a [build and image stream](https://docs.openshift.org/latest/architecture/core_concepts/builds_and_image_streams.html) with this command: + docker build -f images/installer/Dockerfile -t openshift-ansible . - oc new-build docker.io/aweiteka/playbook2image~https://github.com/openshift/openshift-ansible +## Build the Atomic System Container -The progress of the build can be monitored with: +A system container runs using runC instead of Docker and it is managed +by the [atomic](https://github.com/projectatomic/atomic/) tool. As it +doesn't require Docker to run, the installer can run on a node of the +cluster without interfering with the Docker daemon that is configured +by the installer itself. - oc logs -f bc/openshift-ansible +The first step is to build the [container image](#build-an-openshift-ansible-container-image) +as described before. The container image already contains all the +required files to run as a system container. -Once built, the image will be visible in the Image Stream created by the same command: +Once the container image is built, we can import it into the OSTree +storage: - oc describe imagestream openshift-ansible +``` +atomic pull --storage ostree docker:openshift-ansible:latest +``` |