Docker best practice on base images and host os

I have a questition about the best pratices on using docker in production.

In my company we use SLES12 as host os. Should we use SLES also as base for our docker containers?

  • New device node created on host does not get reflected in Docker container when using --device flag
  • Docker-compose with Storm 0.10.0 and Zookeeper (connection loss)
  • Docker Unable to find image '502:20' locally. How can I resolve this issue?
  • Would Docker or Vagrant be help in creating test machine for our enterprise product
  • https is not working on httpd docker container
  • Possible to make incremental checkpoints CRIU
  • In my opinion SLES image is too big to follow the ddocker recommendation for small base images.

    My questition is: Has anyone experience in using docker in production with different host and container os? Are there any disadvantages if we use a small debian/ubuntu base image for our containers? (overhead, security, …)

  • Developing NodeJS app using Docker with live relaod
  • Automatically configure Java to use the maximum RAM allocated to its Docker container
  • Flask Nginx Guincorn/uwsgi docker configuration [closed]
  • How can I delete Docker images by tag, preferably with wildcarding?
  • What is the purpose of running a django application in a virtualenv inside a docker container?
  • Python subprocess — close Django server and Docker container with Ctrl-C, return to terminal
  • One Solution collect form web for “Docker best practice on base images and host os”

    I agree with your assessment that for dockerized applications, smaller base images are preferred. This will save on disk space, reduce network transfer, offer a smaller software surface to worry about security vulnerabilities and general complexity. To my knowledge different host/container distributions is the norm and when they align it’s more of a coincidence than an intentional design. Since the way you interact with the host OS and the container are so very different, even if they were identical, you procedures for keeping things patched would be different. That said, depending on your staff skill set, sticking to the same package manager ecosystem (rpm vs deb) may have some benefit in terms of familiarity of tooling, so finding a small base RPM distro might be a good choice.

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