Kubernetes and Dockerfile

People using Docker have probably used dockerfiles as master templates for their containers.

Does Kubernetes allow re-use of existing dockerfiles? Or will people need to port that to Kubernetes .yaml -style templates?

  • Inspect mysql docker container over ssh tunnel
  • Docker hangs when starting jdubois/jhipster container in OS X
  • Unable to access the internet from Kubernetes containers
  • get docker images command's output with bash script
  • How can I delete Docker images by tag, preferably with wildcarding?
  • kafka on kubernetes cannot produce/consume topics (ClosedChannelException, ErrorLoggingCallback)
  • Docker composed services can't communicate by service name
  • Unable to run docker commands after new docker installation
  • Persistent volumes in docker engine swarm mode across multiple nodes
  • Cannot configure Maven connection from KIE server to Drools workbench using docker-compose
  • SSHFS Mount for Docker Container / Node Server needs to access files on an external server
  • Clone private git repo with dockerfile
  • One Solution collect form web for “Kubernetes and Dockerfile”

    I’m not aware of tools for doing so or people that have been trying this.

    Dockerfiles and the Kubernetes resource manifests (the yaml files) are somewhat orthogonal. While you could pull some information from the Dockerfile to prepopulate the Kubernetes manifest, it’d only be able to fill in a very small subset of the options available.

    You can think of Dockerfiles as describing what is packaged into your container image, while the Kubernetes manifests specify how your container image is deployed — which ports are exposed, environment variables are added, volumes are mounted, services made available to it; how it should be scheduled, health checked, restarted; what its resource requirements are; etc.

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