docker

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
docker [2022-07-24 00:43] – created asdfdocker [2023-02-25 19:35] (current) – asdf
Line 1: Line 1:
-====== Docker reference ====== +====== Docker ====== 
-Eventually need to migrate info from [[https://gist.github.com/bradtraversy/89fad226dc058a41b596d586022a9bd3|this reference]] into a format that makes more sense for me. Also definitely include info on [[https://betterprogramming.pub/running-desktop-apps-in-docker-43a70a5265c4|running desktop apps in docker]]. Maybe cover the JSON outputs of the ''inspect'' commands.+<WRAP center round todo 60%> 
 +Migrate info from [[https://gist.github.com/bradtraversy/89fad226dc058a41b596d586022a9bd3|this reference]] into a format that makes more sense for me. Also include info on [[https://betterprogramming.pub/running-desktop-apps-in-docker-43a70a5265c4|running desktop apps in docker]]. Maybe cover the JSON outputs of the ''inspect'' commands. 
 +</WRAP>
  
 Docker uses a client-server architecture. There is no requirement that the daemon and client be run on the same machine. Docker uses a client-server architecture. There is no requirement that the daemon and client be run on the same machine.
  
 ===== Containers ===== ===== Containers =====
-Docker containers are not full VMs but instead special processes running in the host (on Linux). +Docker containers are not full VMs but instead special processes running in the host (on Linux). Containers have their own filesystems, process trees, and networking hardware, all completely separate from the host's. This isolation makes them immensely useful for running multiple applications with conflicting dependencies or for trying out new software.  
 + 
 +Note that there need not be a one-to-one correspondence between containers and images. A container is a single instance of an image with its own unique resources. Once created, a container can be stopped, started, renamed, destroyed, and so on. 
  
 ===== Images ===== ===== Images =====
-Images contain the app binaries and dependencies, along with instructions on how to build a container.+Images contain the app binaries and dependencies, along with instructions on how to build a container. They are in many ways analogous to git repositories (e.g., push/pull commands, tags).
  
 ===== Volumes and bind mounts ===== ===== Volumes and bind mounts =====
 +Docker allows data persistence through one of two means: //volumes// and //bind mounts//. Bind mounts are exactly what they sound like --- directories on the host that shared directly with the container. Volumes, on the other hand, are completely managed by Docker and have extra functionality. 
 +
 ===== Networks ===== ===== Networks =====
 +
 ===== Dockerfiles ===== ===== Dockerfiles =====
 Much of Docker's flexibility follows from Dockerfile inheritance. Every Dockerfile begins with a ''FROM'' directive indicating a base image. Much of Docker's flexibility follows from Dockerfile inheritance. Every Dockerfile begins with a ''FROM'' directive indicating a base image.
  
 A full Dockerfile reference is available [[https://docs.docker.com/engine/reference/builder/|here]]. A full Dockerfile reference is available [[https://docs.docker.com/engine/reference/builder/|here]].
 +
 ===== Docker Compose ===== ===== Docker Compose =====
 Docker Compose eases the instantiation of multi-container applications. Docker Compose eases the instantiation of multi-container applications.
 +
 +{{tag>software}}
  • docker.1658623421.txt.gz
  • Last modified: 2022-07-24 00:43
  • by asdf