# Build Your Own Container Using Less Than 100 Lines of Go  ## Metadata - Author: [[Julian Friedman]] - Full Title: Build Your Own Container Using Less Than 100 Lines of Go - Category: #articles - Summary: This article series clarifies the technology behind containers and their use in enterprises, addressing common challenges like integration and monitoring. It explains key concepts such as namespaces, cgroups, and layered filesystems that are essential for building containers. The series also looks at future trends in containerization, including the role of unikernels. - URL: https://www.infoq.com/articles/build-a-container-golang/ ## Highlights - The open source release of Docker in March 2013 triggered a major shift in the way in which the software development industry is aspiring to package and deploy modern applications. ([View Highlight](https://read.readwise.io/read/01je2ha27q57w2qd4tw0vnffmz)) - Shipping containers - with their standard shape and size - enable powerful economies of scale and standardisation. And software containers promise many of the same benefits. ([View Highlight](https://read.readwise.io/read/01je2hbdbsftgw0c98h1mw4da4)) - And, really, that’s what containers are about. They’re about bundling up dependencies so we can ship code around in a repeatable, secure way. ([View Highlight](https://read.readwise.io/read/01je2he74ak8f7fm3e1qeehgbj)) - Namespaces provide the isolation needed to run multiple containers on one machine while giving each what appears like it’s own environment. There are - at the time of writing - six namespaces. Each can be independently requested and amounts to giving a process (and its children) a view of a subset of the resources of the machine. ([View Highlight](https://read.readwise.io/read/01jea8xtpe1sebh4e15phv1ea9))