Environment Setup

This section covers the following:

• Signing in to GitHub and forking the workshop repository
• Creating a GitHub Codespace from your fork
• Checking Docker and Docker Compose
• Putting ~/.local/bin on your PATH for tools installed later in the course
• Creating ~/peachycloudsecurity-lab-workspace and running docker run --rm hello-world once to confirm Docker runs containers

If you use GitHub Codespaces, start with Lab: Setup GitHub Codespace. That lab walks you from the public repo through fork, Codespaces, Docker checks, PATH, and workspace creation in one place.

If you run on your own Debian or Ubuntu machine with Docker already installed, skip the Codespace lab and use the blocks below, then open Lab: Workshop workspace.

Tool install path (local Linux)

Downloaded CLI tools in this course install into ~/.local/bin. Add it to your PATH once per profile:

mkdir -p ~/.local/bin
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
export PATH="$HOME/.local/bin:$PATH"

Terminal setup

• Run these in the Codespace integrated terminal (the terminal inside the browser editor). This is still the Linux environment GitHub created for you, not a separate SSH box.

Docker

docker version
docker compose version

• Workspace and hello-world

mkdir -p ~/workspaces/container-security-workshop-lab/peachycloudsecurity-lab-workspace && cd ~/workspaces/container-security-workshop-lab/peachycloudsecurity-lab-workspace
docker run --rm hello-world

You should see the hello-world completion text. That only checks that Docker can pull and run an image from this Codespace.

• Cleanup

docker rmi hello-world

Note on CPU architecture

Several labs download pre-built binaries with curl. URLs often target x86_64 (amd64). On arm64 hosts, use the arm64 build from the same release page when the vendor publishes one. Individual labs call this out where it matters.

• Next step: Lab: Setup GitHub Codespace if you use Codespaces, otherwise Lab: Workshop workspace.