This is a starting point for C solutions to the "Build Your Own Docker" Challenge.
In this challenge, you'll build a program that can pull an image from Docker Hub and execute commands in it. Along the way, we'll learn about chroot, kernel namespaces, the docker registry API and much more.
The entry point for your Docker implementation is app/main.c. Study and
uncomment the relevant code, and push your changes to pass the first stage:
git add .
git commit -m "pass 1st stage" # any msg
git push origin masterThat's all!
Note: This section is for stages 2 and beyond.
You'll use linux-specific syscalls in this challenge. so we'll run your code inside a Docker container.
Please ensure you have Docker installed locally.
Next, add a shell alias:
alias mydocker='docker build -t mydocker . && docker run --cap-add="SYS_ADMIN" mydocker'(The --cap-add="SYS_ADMIN" flag is required to create
PID Namespaces)
You can now execute your program like this:
mydocker run ubuntu:latest /usr/local/bin/docker-explorer echo heychild process and fork
You'll now pipe the program's stdout and stderr to the parent process.
Like the last stage, the tester will run your program like this:
mydocker run ubuntu:latest /usr/local/bin/docker-explorer echo hey
To test this behaviour locally, you could use the echo + echo_stderr commands that docker-explorer exposes. Run docker-explorer --help to view usage.
- linux system calls
- linux library calls
- pipe[] in c
- types.h library in c
- wexit status
- child process and fork
In the previous stage, we executed a program that existed locally on our machine. This program had write access to the whole filesystem, which means that it could do dangerous things!
In this stage, you'll use chroot to ensure that the program you execute doesn't have access to any files on the host machine. Create an empty temporary directory and chroot into it when executing the command. You'll need to copy the binary being executed too.
Just like the previous stage, the tester will run your program like this:
- chroot