Skip to content - Image – “An image is an executable package that includes everything needed to run an application–the code, a runtime, libraries, environment variables, and configuration files.” (source)
- Container – “A container is a runtime instance of an image–what the image becomes in memory when executed (that is, an image with state, or a user process).” (source)
- Container ID – A SHA-256 unique ID for a container.
- Containerization
- Dockerfile – “Defines what goes on in the environment inside your container. Access to resources like networking interfaces and disk drives is virtualized inside this environment, which is isolated from the rest of your system, so you need to map ports to the outside world, and be specific about what files you want to “copy in” to that environment.” (uncertain source)
- Exposing a Port
- Nodes – Each machine in a swarm.
- Process ID
- Publishing a Port
- Service – Provides a specific portion of a distributed application (e.g. web server, database server, etc.)
- “Services are really just “containers in production.” A service only runs one image, but it codifies the way that image runs—what ports it should use, how many replicas of the container should run so the service has the capacity it needs, and so on.” (source)
- Stack
- Swarm – A Dockerized cluster of multiple machines.
- Swarm Manager – Only machines able to execute commands, authorize other machines to join.
- Task – “A single container running in a service.” (uncertain source)
- Virtual Machine
- Virtualization
- Workers – Machines that aren’t Swarm Managers.