Let's briefly explore how these two Docker images work.įirst, start up an instance of the docker:dind image:ĭocker run -privileged -p 12375:2375 -e DOCKER_TLS_CERTDIR="" docker:dind While typically not needed on development machines or even in deployed environments, this can be quite handy for continuous integration (CI) environments where isolation from other build jobs is a must. This means that you can run new instances of the Docker daemon and Docker client to create your own isolated Docker workspace. Simply put, the stable flavor of the docker image is intended to be used as a Docker client, and the dind flavor is intended to be used as a Docker daemon. That is to say, when you run docker on the command line, you're using the Docker client, which connects to a Docker daemon (usually running on localhost port 2376 or 2375, depending on whether TLS is or is not enabled, respectively). What is this image for and what is the purpose of these two different image tags?ĭocker, it's important to note, uses a client/server architecture. ![]() It also has two flavors, "stable" and a "dind" (Docker-in-Docker). ![]() ![]() ![]() There exists on Docker hub a Docker image called docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |