3 years ago

Category: Software, Kubernetes, Ubuntu, Docker, containerization, github

Ever since Docker released it’s first version back in 2013, it triggered a major shift in the way the software industry works. You can use Docker Containers to wrap up an application in such a way that its deployment and runtime issues- how to expose it on a network, how to manage its use of storage and memory and I/O, how to control access permissions, etc.

When I run an Ubuntu container, we can see that it has it’s own hostname and it’s own set of processes: This means that our Ubuntu container is running in an isolated environment.

We are essentially creating a copy and calling it again by appending the string 'child' to it followed by the rest of the arguments that we received in run().

We will now have to let our container know about this filesystem and ask it to change it’s root to this copied filesystem.