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, they are helpful.

  • How to disable sticky sessions in Openshift3
  • docker behind proxy doesn't use system proxy info
  • Docker ignores patterns in .dockerignore
  • Docker: readonly filesystem error
  • What is driver name of docker for mac?
  • Kubernetes: Directly connecting a container to an external IP for UDP connections?
  • 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 ?

  • Using golang connect to docker container with functional tty
  • Docker Cloud Wordpress stack workflow optimization
  • HDFS data node connection error in a docker container
  • How can I use an ephemeral volume for a Docker container using an official MySQL image with docker-compose?
  • Ansible docker module picks random port by default
  • Mapping docker port is failed
  • One Solution collect form web for “architechtetural thoughts about dockerizing the exsting services”

    There are lots of 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.