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.
BuildKit is the build engine used by docker build (and docker buildx build). It’s more than “a Dockerfile builder”: it executes a content-addressed DAG of build steps, which enables aggressive caching and parallel execution.
From Host
Python code can have imports that do not exist in the environment (pipenv) but do exist in a Docker container. We can copy the requirements.txt file from within the Docker container and then use pip to install them.
Create Dockerfile
Printing all socket information:
When developing features for certain applications (where these application are run as containers, e.g. KEDA, Dapr), we need to create a new Docker image to test out our changes. This guide explains how to do that using Google Cloud Artifact Registry and Amazon Web Services ECR.
Get Basic Auth from Token
Get container ID (leftmost column)
Configuration
Serving Static Content
Log in:
Start MongoDB Container
Docker uses /var/lib/docker to store your images, containers, and local named volumes
Set up sidecar container with tcpdump:
Add the following flag: