This project is meant to highlight the current metadata issue with docker versions 1.9+ and Openshift 3.1
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
ansible
openshift
support/docker
vagrant
.gitignore
Dockerfile
README.adoc
Vagrantfile

README.adoc

Docker and OpenShift Issues

With the continual updating of docker without backwards compatibility has really put many systems in a quandary. This project is one example of a workaround specifically for OpenShift.

Vagrant

  1. Start box

$ vagrant up

Build Docker images via 1.8.2 engine

SSH onto vagrant box

indigo-ros-core
$ cd /vagrant/docker/indigo-ros-core
$ sudo docker build -t jmarley/indigo-ros-core:docker1.8 .
$ sudo docker push
indigo-ros-base
$ sudo docker build -t jmarley/indig-ros-base:docker1.8 .

OpenShift Setup

Add Service Account
$ oc create -f openshift/serviceaccount.yaml
Add Security Control Context
$ oc create -f openshift/scc_ros.yaml
Update scc policy changes
$ oc adm policy add-scc-to-user scc-ros <user> -n <project>
Create image streams
$ oc create -f openshift/imagestream-indigo-ros-base.yaml
$ oc create -f openshift/imagestream-docker-openshift-issues.yaml
Create Build configurations
$ oc create -f openshift/buildconfig-docker-openshift-issues.yaml
Create Deploy configuraitons
$ oc create -f openshift/deployconfig-docker-openshift-issues.yaml

Working Environment

  1. added robot read in quay

  2. added .docker/config.json with creds

  3. updated BuildConfig.yaml

  4. rebuild images in 1.8 docker engine

Status

Docker Repository on Quay