Containers are everywhere now a days. We want to use containers during development, in staging, in production, etc. However, it’s not that straight forward, thanks to the plethora of container runtimes and toolchains. Some are developer friendly, whereas, others, which are battle tested for production, are not that developer friendly. In this talk we’ll walk you through the current state of things for containers in various environments: development, production, etc., the disparity between container technologies usually used in development and production, how to take things from development to production, etc. This will showcase how Red Hat, Skippbox and Google have been working to solve this problem, and the result of that work is a CLI tool called Kompose, https://github.com/skippbox/kompose. Kompose takes in docker-compose file format and generates Kubernetes and OpenShift artifacts. However, is it enough? We need a standardized specification to define multi container applications that works seamlessly across multiple container runtimes and orchestration tools.

This talk will be organized as follows:

Developer workflow with containers Container technologies preferred in production What it takes to have a production like environment for development? So much to learn! Pushing application to production with 0 (or little) learning curve Kompose: Tool to move from docker-compose to Kubernetes What next? A standard specification to define multi-container application Road to container Utopia