The easiest way to understand what a container is is to think of it as a process that runs on our machine, isolated from other processes.
To make this happen, Linux namespaces and cgroups are used under the hood.
... 1/4
A container has its own dedicated filesystem, provided by an image.
The image contains:
-dependencies
-configuration
-binaries
-environment variables
-other important data related to the container to be instantiated.
Many containers can be run from a single image
... 2/4
Technically, a container is first created, then, started.
To do this with a single command, we can use the 'docker run' command.
to see all the containers running on the host:
'docker container ls -a'
or just
'docker ps -a'
... 3/4
To run a container, we need the image.
If we use the `docker run` command, but the image is NOT on our filesystem, Docker looks for it in the public registry (Docker Hub), and it downloads the image (pull).
to see the images:
`docker image ls`
or just
`docker images`
... 4/4
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The instruction is not case-sensitive, but the convention is to be UPPERCASE to distinguish them from arguments more easily.
add # to add a single-line comment
... 2/25
.dockerignore
Before sending the context to the Docker daemon, the Docker CLI checks if a .dockerignore file is in the root directory. If so it excludes files/dirs that match patterns in it.
The Docker client talks to the Docker daemon (server), which menages different docker objects:
- Images
- Containers
- Networks
- Volumes
Let's see in details:
... 1/12
The Docker client and the daemon can run on the same system, or they can be connected remotely using HTTP protocol.
The connection is established using REST APIs, over UNIX sockets/network interface
... 2/12
DOCKER DAEMON (SERVER)
The Docker daemon (dockerd) is a process, which runs in the background, that manages the docker objects (images, containers, networks, volumes). It processes Docker API requests
I will definitely use it for the next projects that will include a frontend.
A Thread of my impressions 🧵
✅SIMPLE = GOOD
The first thing that struck me was the simplicity with which it can be integrated into a simple project.
It is from this that we know if a Framework will be successful and I'm sure it will.
I don't know why something like this hasn't existed for a long time
🛠️CUSTOMIZATION
I was expecting something like bootstrap but improved instead the approach is completely different.
Yes in Bootstrap you can always customize the elements, but I always found it complicated and every time I found myself rewriting the same custom classes.