Docker Containers

Definition: A Docker container is a runnable instance of a Docker image. Containers are isolated environments that run applications with all their dependencies.
Usage: Containers are used to run applications in isolated environments. They can be started, stopped, and removed independently of each other.
Lifecycle: Containers are created from images using the docker run command. They can be started, stopped, restarted, and deleted as needed.

Certainly! Here is a short markdown note for Obsidian that explains the difference between bind mounts and named volumes in Docker:

Docker: Bind Mounts vs. Named Volumes

Bind mounts link a directory or file from the host filesystem into the container.
Useful for development purposes, where changes in your local filesystem should be reflected in the container instantly.

Direct Path Mapping: Directly reference a path on the host machine.
Real-Time Sync: Changes on the host are immediately reflected inside the container.
No Definition Needed: Does not need to be defined in the volumes section of docker-compose.yml.

Named volumes are managed by Docker and stored in a Docker-managed location on the host.
Useful for persisting data beyond the lifecycle of a single container.

Docker-Managed Storage: Stored in Docker-specific locations (e.g., /var/lib/docker/volumes/ on Linux).
Persistence: Data remains intact even if containers are removed.
Definition Required: Must be defined in the volumes section of docker-compose.yml.

Bind Mounts:
- Ideal for development environments.
- Direct path mapping from host to container.
- No need for explicit volume definition.
Named Volumes:
- Ideal for persisting data.
- Managed by Docker.
- Requires explicit volume definition for clarity and management.

Feature	Docker Images	Docker Volumes	Docker Containers
Purpose	Blueprint for containers	Persistent storage for container data	Running instances of images
Mutable	No (immutable once created)	Yes (data can be changed)	Yes (state changes during runtime)
Creation	Built from Dockerfiles	Created via Docker CLI or Docker Compose	Created from Docker images
Storage	Stored in image registries (e.g., Docker Hub)	Stored on host filesystem	Exist in memory and disk as long as running
Isolation	Provides consistent environment	Shares data across containers and host	Isolated environment for application
Usage	Basis for creating containers	Persistent data storage	Run applications in isolated environments

Docker Images are the templates used to create containers.
Docker Volumes provide persistent storage that can be shared between containers and the host.
Docker Containers are the running instances of Docker images that execute applications in isolated environments.