4 ms·
These articles where someone uses Linux kernel level features to replicate Docker isolation are as old as Docker itself, and in my experience they always miss o
by giobox 3y ago
These articles where someone uses Linux kernel level features to replicate Docker isolation are as old as Docker itself, and in my experience they always miss one of the most critical parts of the Docker ecosystem - the easily hackable and extensible container image format.
It's the ease of extension of the container image format that is as much responsible for the popularity of container based architectures as it is clever use of namespaces, cgroups and chroot for "robust isolation, resource management, and security". Without the image format, Docker is way less interesting and you arguably haven't "built your own Docker".
- deleted 3y ago[deleted]
- rewmie 3y ago> (...) they always miss one of the most critical parts of the Docker ecosystem - the easily hackable and extensible container image format. Exactly this. Docker might have a ton of nifty features, but it's killer feature is undoubtedly app packaging and deploying. Features like chroot are already as old as time, but they never became nearly as popular as Docker for a good reason: they don't solve the problem most people need to get out of the way before being able to containerize apps.
- arnaudperalta 3y agoReplace every occurrence of 'Docker' in this article by 'containerd' and it's a match !