Docker Best Practises: at what size application should you refrain from containerising?

In my ongoing quest to Containerize All The Things, I’ve played with and installed some pretty hefty images. Not as crazy as what Jessie Frazelle does, but still.

I have one that is 1.8 GB in size at which it hit me whether I may be heading into anti-pattern territory. I mean, where does it end? Dockerize the entire suite of Oracle products?!

  • How can I run a docker container on localhost over the default IP?
  • how to notify error for `restart: on-failure` in docker-compose?
  • kubernetes cannot pull local image
  • Docker build argument
  • Connect to docker-machine using docker-py (OSX)
  • How to get the service IP in Kubernetes?
  • Is there an advisory, guideline, best practise guide, anything that states at what point you should just stick with good old servers, VMs or similar?

    I ran across a blog that said that SQL database servers is pretty much one where it’s not worth it: by nature they are not immutable and you’re looking at lots of mapped volumes anyway. Naturally I can’t find that blog anymore. 🙁

    At one point I ran nearly the entire suite of Atlassian products (Bitbucket, Jira, Confluence, Bamboo) in containers, with massive docker run command lines to get all the mappings and environments settings in. I stopped doing it when I just couldn’t see the advantage.

    Is there a good rule of thumb? A simple formula that encompasses, say, immutability and size to arrive at a “OK to containerise/DON’T containerise” table?

  • Docker-compose Predis not connection via PHP
  • running incorrect docker image osx
  • How to get maven version in Jenkins pipeline
  • How to force pull docker images in DC OS?
  • Docker LAMP Stack
  • Gitlab always shows “No container image repositories in Container Registry for this project.”
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.