Build Docker Image for Minikube
β Last Updated : September 20, 2022
πͺ Prequisite Knowledge (Optional)
Upload[Minikube InQuick ProgressStart](Minikube Quick Start 872ac022c97f4d7480709dea8e5bb64b.md)
[Containerization / Docker](Containerization Docker 2e0ce73ff63b419d9e2782d79c4cc440.md)
[Building Unity Headless Docker Image](Building Unity Headless Docker Image 45ec56a4f4bb4e9a88414df175ae7885.md)
β Key Question / Problem / Issue
Minikube have different image registry daemon that differ from common docker daemon to fetch it images from
β Expected Output/Definition of Done
information, trick or guideline on how to push the interact (CRUD) docker image in minikube daemon
π Resulting Solution
Docker architecture
Docker uses a client-server architecture. The Docker client talks to the Docker daemon, which does the heavy lifting of building, running, and distributing your Docker containers. The Docker client and daemon can run on the same system, or you can connect a Docker client to a remote Docker daemon. The Docker client and daemon communicate using a REST API, over UNIX sockets or a network interface. Another Docker client is Docker Compose, that lets you work with applications consisting of a set of containers.
Docker Daemon
The Docker daemon (dockerd) listens for Docker API requests and manages Docker objects such as images, containers, networks, and volumes. A daemon can also communicate with other daemons to manage Docker services.
Minikube Docker Daemon
When using a container or VM driver (all drivers except none), you can reuse the Docker daemon inside minikube cluster. This means you donβt have to build on your host machine and push the image into a docker registry. You can just build inside the same docker daemon as minikube which speeds up local experiments.
#this will tell Docker Client to use Docker Daemon inside Minikube
& minikube -p agones docker-env | Invoke-Expression
#this build will be executed by Minikube's Docker Daemon
docker build -t unity-headless .