devspace Devspace docker images should be built by docker hub

Automatic builds should be configured for each of the Dockerfiles in this repo.

Sep 19 '17 09:09 manics

As confirmed by ome-files-py we can certainly create multiple Docker Hub repositories pointing at this GitHub repositories using various Dockerfile locations. Would the end goal be to test the building of the images or to consume upstream images rather than rebuilding it every time at deployment time? Should the images be named as devspace_<container> e.g. devspace_web, devspace_testintegration...

Sep 19 '17 10:09 sbesson

The goal is to have images in a registry for people to use instead of rebuilding. Docker Hub is obviously the most convenient but we could setup our own registry if preferred. If we start running devspace with any orchestration solution on a cluster including Kubernetes or Swarm a central registry is required as a source for images.

Sep 19 '17 11:09 manics

:+1: for using Docker Hub initially (probably makes this issue a duplicate of https://github.com/openmicroscopy/devspace/issues/25). Would that mean decoupling some of the logic into separate repositories (docker_jenkins, docker_omero...) and have this repo composing various base images?

Sep 19 '17 19:09 sbesson

Whatever's easiest to get this working, and refactor later?

Sep 20 '17 08:09 manics