architechtetural thoughts about dockerizing the exsting services

we are in the process of dockerizing existing services those use kafka, storm
and the expectation is use to create dockerized builds by integrating with jenkins .

I happened to look at a couple of articles http://blog.howareyou.com/post/62157486858/continuous-delivery-with-docker-and-jenkins-part, they are helpful.

  • Right way to delete unused docker images on OpenShift Origin
  • ManageIQ web application inside docker container can’t connect to Hawkular outside container
  • COPY doesn't work on Docker prod
  • Dockerfile: mkdir and COPY commands run fine but I can't see the directory and file
  • How to use Docker Remote API to assign a static IP address to a container
  • How to copy folders to docker image from Dockerfile?
  • I wanted to know the experiences with docker and how much time it took for the dockerizing a typical solution. And are there any best practices ?

  • Ruby and Rails “path not found” when installed using RVM on Docker
  • boot2docker equivalent of docker exec
  • Docker Proxy Setup
  • Django Server wont launch in Docker-Compose
  • how to securely connect to a mysql server running on a virtual machine
  • Adding sphinx container docker-compose shows an error
  • One Solution collect form web for “architechtetural thoughts about dockerizing the exsting services”

    There are lots of best practices: https://docs.docker.com/articles/dockerfile_best-practices/

    I think the “time to dockerize” will depend a lot on how familiar you are with linux. If you’re already used to setting up linux systems, it should be pretty fast.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.