7 KiB
Basic usage
docker run hello-world
First time won't have the image to run container, will fetch from Docker Hub
See running processes (add -a flag for historic):
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
64d92f77c12f hello-world "/hello" About a minute ago Exited (0) 19 seconds ago frosty_moser
d6c54f7801fe cda/node-16 "docker-entrypoint.s…" 3 months ago Exited (255) 50 minutes ago 0.0.0.0:3000->3000/tcp, 0.0.0.0:3002->3002/tcp cda-node-16
ddb15b93b47e cda/mysql-5.7 "docker-entrypoint.s…" 3 months ago Exited (255) 50 minutes ago 33060/tcp, 0.0.0.0:33066->3306/tcp cda-mysql-5-7
567f35be3762 cda/mysql-5.7 "docker-entrypoint.s…" 3 months ago Exited (255) 50 minutes ago 33060/tcp, 0.0.0.0:33067->3306/tcp cda-mysql-5-7-testing
dc8dca198f07 bitnami/minio:latest "/opt/bitnami/script…" 3 months ago Exited (255) 50 minutes ago 0.0.0.0:9000-9001->9000-9001/tcp cda-minio
9397d4c72679 opensearchproject/opensearch:1.3.7 "./opensearch-docker…" 3 months ago Exited (255) 50 minutes ago 0.0.0.0:9200->9200/tcp, 9300/tcp, 0.0.0.0:9600->9600/tcp, 9650/tcp cda-opensearch
```
Each container will be designated with a GUID and a random name for ease of reference
First lab:
Key learnings:
Give custom name
docker run --name my-custom-name hello-world
Remove all containers
docker container prune
A "dangling" image is an unused image - one that is not associated with a container. Remove dangling images with
docker image prune
Unit 3: Containers in depth
docker run implicitly means run within container but you can specify networks and other docker objects.
docker run debian /bin/echo "Hello, world"
Creates and runs a container from an image called debian and executes /bin/echo inside of it.
Once you have run this. If successful it will exit. The container will stop running (exit) but the container will still be in memory.
When run is used it grabs the image and constructs and starts a container using it.
It's actually combining two commands:
docker create --name my_container hello-world
docker start my_container
You can also run a container as a daemon. The container will run in the background and detaches it from the console:
docker run -d debian /bin/sh -c /bin/sh -c "while true; do echo 'Hello!'; sleep 1; done"
This will log every second
What will acutally be output is the container ID:
2749d796cbd64e9cf57307329e792587c39d8244f2377e62d78f3f3f77eecdb4
docker log 2749
hello
hello
hello
This will keep running in an infinite loop until:
docker stop 274
There will be a delay because it shuts down gracefully. It sends a SIGINT to the process in the container with PID 1 (i.e the root or parent process for the container)
stop keeps it in memory so it can be restarted and you can examine the logs.
if you use docker rm 274, it cannot be becovered and the logs are deleted.
We can tell Docker to immediately remove a container after it exits:
docker run --rm [container]
Container lifecycle
//TODO : Add diagram of lifecycle.
Interacting with containers
In the examples so far the container is a closed box. You don't have a terminal through which you can interact with the container as you would with an OS.
For images that have an OS we can use -i -t to launch a terminal in interactive mode.
docker run -i -t debian /bin/bash
root@0022da12f2f2:/# ls
bin boot dev etc home lib media mnt opt proc root run sbin srv sys tmp usr var
root@0022da12f2f2:/# whoami
root
root@0022da12f2f2:/# ls usr/
bin games include lib libexec local sbin share src
Note that it defaults to the root user.
Containers are lightweight and should only contain the minium environment needed to run an application.
Many programs and processes will not be there by default for this reason. Although you could install a package manager and install the commands you need.
If the container is already running, you can access it via the exec command.
docker exec -i -t my_container bash
If a container is running in detached mode we can attach to the main process with docker attach
docker attach my_container
Container troubleshooting
Lots of diagnostic output:
docker inspect container_name
List processes (from outside):
docker top container_name
View logs
docker logs container_name
Resources
https://www.taniarascia.com/continuous-integration-pipeline-docker/
Unit 4: Docker images
Docker needs an image to run a container. Images are stored in the local registry. If it can't find it, it will try and pull it from Docker Hub.
List images:
docker images
docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
debian latest e6d9c9c3e100 12 days ago 118MB
ubuntu latest bab8ce5c00ca 6 weeks ago 69.2MB
cda/mysql-5.7 latest 312ce2a6cea5 3 months ago 495MB
cda/node-16 latest b26e54c8fa11 3 months ago 1.44GB
bitnami/minio latest ef6d14df2158 3 months ago 229MB
opensearchproject/opensearch 1.3.7 0f8ef57c3629 4 months ago 831MB
hello-world latest 46331d942d63 13 months ago 9.14kB
When you specify the name of an image, you are referring to the repository. The registry is the list of repositories available on the Docker Hub.
Eg:
docker run -it ubuntu:18:04 /bin/bash
ubuntuis the image repository18.04is the image tag
Without specifying a tag, Docker will default to latest.
Docker images also support different platforms, e.g. arm64, amd64
Docker will try to pull the image for your platform.
Linux-based Intel processors are represented by amd64
Examine image details:
docker image inspect
Remove an image:
docker rmi
Anatomy of an image
An image is not a single file but a series of read-only layers like an onion. When you pull an image, you will see multiple GUIDs listed in the terminal. Each one of these is a layer.
Each layer represents an incremental change to the previous layer. The first layer is the base layer and the layers on top are called intermediary layers. Each layer is hashed as a digest. This proves that the layer has not been manipulated.