Kaniko Tutorial : Build container images without Docker Daemon
Google has recently introduced Kaniko, an open-source tool for building container images from a Dockerfile even without privileged root access. If you’ve noticed, Docker daemon always runs as the root user. It actually binds to a Unix socket instead of a TCP port.
By default, Unix socket is owned by the user root and other users can only access it using sudo command. With kaniko, we can build an image from a Dockerfile and push it to a registry without root access. Since it doesn’t require any special privileges or permissions, it can be run in an environment that can’t have access to privileges or a Docker daemon.
With this context, let’s try and understand how it works and build a container image using Kaniko tool.
Cross-posted from: New Stack
How it works?
Kaniko runs as a container and takes in three arguments: a Dockerfile, a build context, and the name of the registry to which it should push the final image. It fetches and extracts the base-image file system to root (the base image is the image in the FROM line of the Dockerfile). It executes each command in order and takes a snapshot of the file system after each command.
Kaniko unpacks the filesystem, executes commands, and snapshots the filesystem completely in user-space within the executor image. Since its running inside user-space, it avoids requiring privileged access on your machine, and also docker daemon or CLI is not involved.
Build container images using Kaniko
The recommended way to set up kaniko is to use the readymade executor image which can be started as a Docker container or as a container within Kubernetes.
docker run \ -v <path-on-host>:<path-inside-container> \ gcr.io/kaniko-project/executor:latest \ --dockerfile=<path to dockerfile> \ --context=<path-inside-container> \ --destination=<repo with image name>:<tag>
Devops Engineer Masters Program will make you proficient in DevOps principles like CI/CD, Continuous Monitoring and Continuous Delivery, using tools like Puppet, Nagios, Chef, Docker, Git & Jenkins. It includes training on Linux, Python, Docker, AWS DevOps Certification Training and Splunk. The curriculum has been determined by extensive research on 5000+ job descriptions across the globe.
-vindicates path to Dockerfile and its dependencies + Path to be used inside the container
gcr.io/kaniko-project/executoris the Kaniko executor
--dockerfilepath to the Dockerfile (including the file name)
--context pathto the mounted directory (inside the container)
--destinationrepresents the full URL to the Docker Registry with Image name : Tag
docker run \ -v $(pwd):/usr \ gcr.io/kaniko-project/executor:latest \ --dockerfile=OrdAppDockerfile \ --context=/usr \ --destination=localhost:5000:5.1
Image – Building container image using KanikoIf authentication is enabled on your destination registry then mount the local Docker
config.json file to the kaniko container, so that it can authenticate with the credentials for the destination Docker Registry.
In this article, you have learned how to build Docker images using Kaniko without using Docker.As always, there is much more to the Kaniko tool than what was covered here, but now you would have got a good insight on basics. Also please keep in mind that kaniko is under ongoing development and maybe not all commands from the Dockerfile are supported currently.
Like this post? Don’t forget to share it!
- kaniko-users Google group
- Kaniko GitHub repo
- Using Docker Application Packages to Deliver Apps across Teams
- Docker tutorial – Build Docker image for your Java application
- How to aggregate Docker Container logs and analyse with ELK stack ?
- Implementing secure containers using gVisor+Docker tutorial
- Google Cloud Courses Collection