#docker
9pieces
- 01 ·→
Getting Docker running
Get Docker installed and make sure everything is set up by running your first container.
- 02 ·→
What Docker actually is
A container is a normal process wearing a blindfold. Here is what the kernel is doing, and why that matters when you are the one holding the shell.
- 03 ·→
A tool for every job
Run any tool at any version without trashing your host, and stop maintaining five Pythons.
- 04 ·→
Build for hardware you do not have
Bind mount your working directory into a container, then statically compile an exploit for an architecture you own no hardware for.
- 05 ·→
Your own attack image
Write a Dockerfile once and stop paying for apt-get on every run. Layers, cache, and a Kali image that starts in a second.
- 06 ·→
Container networking
Bridge, host, none, and sharing another container's stack. We have so many network options.
- 07 ·→
A lab in one file
Two targets, two subnets, one attacker container, and a pivot. Compose gives you a segmented network to practise on in about thirty seconds.
- 08 ·→
Docker as an attack surface
A mounted socket, a privileged flag, or a shared PID namespace. Three ordinary looking configurations that each hand you the host.
- 09 ·→
Tearing it down
Reclaim the disk Docker quietly ate, and move a built image onto a machine with no internet.