-
Notifications
You must be signed in to change notification settings - Fork 70
Newbie
If you are new to Clear Containers, try working through the following tasks. They should help you to become familiar with the system.
- Read the project's README carefully.
- Read the architecture document for a technical overview and details of the system components.
- Install Clear Containers.
- Check that Clear Containers has installed, and is available in
docker
(hint:docker info
). - Create a Clear Container (hint:
docker run
as normal! :) - Prove that you are running a Clear Container (hints:
uname -r
andps aux | grep qemu
).
-
Run
sudo cc-runtime cc-check
and seeing if you understand all the output(see https://github.com/clearcontainers/runtime#hardware-requirements).
-
Run
sudo cc-runtime cc-env
and seeing if you understand all the output(see https://github.com/clearcontainers/runtime#configuration).
- Enable debugging.
- Find a way to force an error (hint: Try adding spurious data into the config file).
- Ensure you get a useful error message returned to you.
- See if you can find evidence of the error you forced [in the logs] (https://github.com/clearcontainers/runtime#logging).
ℹ️ Note:
This section assumes you have read the architecture document.
Clear Containers uses a small root filesystem (rootfs
) image (which can be based on any Linux distro) and a guest kernel image to boot the virtual machine. If you wish, you can generate your own custom rootfs
and / or custom kernel
. This exercise gets you to create a custom rootfs
image and boot a Clear Container using it.
- Create a new
rootfs
image using osbuilder. - Read the osbuilder docs to establish how to modify your runtime configuration to use the new
rootfs
image. - Start a Clear Container using your new
rootfs
image. - Find a way to prove that you are using your new image.
If you come across any issues or you have thoughts on how we can improve the system, please raise an issue so we can help! 😄
Usage
Development
Process