Facts DOCKER Install (do not circulate)
by
pkjr002
e-marshall
kemccusker
⚠️ This content is intended for human readers only. Automated
scraping, data extraction, or use by large language models (LLMs)
without explicit permission is not allowed.
© 2026 by pkjr002.
Before you begin, make sure your machine meets the requirements below. All links open the official install pages.
| Item | Minimum | Recommended |
|---|---|---|
| Free disk space | ~32 GB | 60 GB (full module data), AR6 requires 2.7 TB |
| RAM | 2 GB | 64+ GB |
| CPU | 2 processors | 50 processors |
| Tool | Why you need it |
|---|---|
| Operating system | macOS, Linux, or Windows |
| Docker Desktop | Builds and runs the FACTS container. |
| Git | Clone the FACTS repository. |
| VS CODE / IDE (optional) | You can use vi or nanao etc in the terminal if you are superuser, I find it easier to edit config and experiment files in IDE's. |
docker --version # should print Docker version 20.x or newer
docker run hello-world # confirms Docker daemon is running
git --version # should print git version 2.x or newer
This cookbook uses Git to clone the FACTS repo. If you are new to Git, checkout this cheatsheet : BASIC_git.
Git is a local version control system that allows developers to track changes to code, collaborate on projects, and manage source code history.
GitHub is a web-based platform built on top of Git that provides tools for hosting, sharing, and collaborating on Git repositories.
git clone <repo-url> # download a repo
git status # see what changed
git checkout <branch> # switch branches
git pull # fetch + merge latest from remote
git log --oneline -n 10 # last 10 commits
Docker is a tool that packages software and all of its dependencies into a self-contained unit called a container. A container behaves like a lightweight, isolated mini-computer that runs the same way on any machine (macOS, Linux, Windows, HPC), removing the classic “it works on my laptop” problem.
Two key concepts:
Click each section below to expand the commands.
docker images # list all images
docker ps # list running containers
docker ps -a # list all containers (running + stopped)
docker start <container_id_or_name> # start a stopped container
docker stop <container_id_or_name> # stop a running container
docker exec -it <container_id_or_name> /bin/bash # open a shell inside a running container
docker rm <container_id_or_name> # remove a stopped container
docker rm -f <container_id_or_name> # force remove (even if running)
docker rmi <image_id_or_name> # remove an image
docker rmi -f <image_id_or_name> # force remove
docker system prune # remove stopped containers, unused networks, dangling images
docker system prune -a # also remove all unused images (be careful)
💡 For more hands-on Docker examples and container recipes, see pkjr002/BASIC/BASIC_Containers.
Last updated: 2026-05-18 · Crrent guide author: pkjr002