grep -i pid /proc/${PID_OUTSIDE_DOCKER}/status
# then look at NSpid line to see if it contains the PID inside Docker
https://stackoverflow.com/questions/52021956/get-internal-docker-pid-by-system-pid
sudo usermod -aG docker $USER
newgrp docker
docker container ls -a
https://docs.docker.com/engine/reference/commandline/container_ls/
# SIGTERM first, then SIGKILL after 10 seconds
docker stop <container>
# SIGKILL right off the bat
docker kill <container>
https://www.ctl.io/developers/blog/post/gracefully-stopping-docker-containers/
docker image inspect <IMAGE_NAME>
https://docs.docker.com/engine/reference/commandline/image_inspect/
docker ps # to see running contains
docker logs <CONTAINER_ID>
Generally want to use up
to start everything. run
is for running specific services and their dependencies. start
is for starting stopped services.
https://docs.docker.com/compose/faq/#whats-the-difference-between-up-run-and-start
Remember to start Docker program in Applications first.
docker image load -i <file>
docker images
# -i means interactive
# -t means "Allocate a pseudo-TTY"
docker run -it <rhel-image> bash