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?

  • linking kibana with elasticsearch
  • create importable Python module in Docker container
  • Hide/obfuscate environmental parameters in docker
  • Docker compose with subdirectory and live reload
  • How is docker able to mount a volume from docker client into a docker container running on docker host?
  • How to mask multiple Docker containers to a single public IP on Windows 10/ Server 2016
  • Unable to run Registrator using docker-compose. Get connection refused error
  • can't connect to local mysql server through socket while running db using volume
  • Docker Configuration´╝Üdocker.service vs daemon.json
  • Docker kill an infinite process in a container after X amount of time
  • How to install nvm in a Dockerfile?
  • Docker compose and concurrent integration testing
  • 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.