I guess so, but it's kind of like saying that a database is just a list of data that you can search. It's the tooling around containers that make them useful. One of the most useful things about...
I guess so, but it's kind of like saying that a database is just a list of data that you can search. It's the tooling around containers that make them useful. One of the most useful things about Docker is that there's tools that will allow you to run the exact same code even on systems that aren't running a Linux kernel.
I think that's exactly right. At the end of the day, containers are just cgroups with tooling, which the writer definitely undersells. The degree of process isolation in cgroups far exceeds...
I think that's exactly right.
At the end of the day, containers are just cgroups with tooling, which the writer definitely undersells. The degree of process isolation in cgroups far exceeds anything from chroot. Calling them lightweight VMs is less-incorrect than the article title.
Containers are more akin to BSD jails than chroot. And BSD jails didn't catch on in the same way as Linux containers in part due to that lack of tooling. I ended up doing a massive migration off FreeBSD at home because that lack of tooling hurt a lot more than any of the other benefits of FreeBSD.
A more apt title for this article would be "I reverse engineered container tooling to use a chroot". But a lot of people could elaborate more on why that's a bad idea.
I guess so, but it's kind of like saying that a database is just a list of data that you can search. It's the tooling around containers that make them useful. One of the most useful things about Docker is that there's tools that will allow you to run the exact same code even on systems that aren't running a Linux kernel.
I think that's exactly right.
At the end of the day, containers are just cgroups with tooling, which the writer definitely undersells. The degree of process isolation in cgroups far exceeds anything from chroot. Calling them lightweight VMs is less-incorrect than the article title.
Containers are more akin to BSD jails than chroot. And BSD jails didn't catch on in the same way as Linux containers in part due to that lack of tooling. I ended up doing a massive migration off FreeBSD at home because that lack of tooling hurt a lot more than any of the other benefits of FreeBSD.
A more apt title for this article would be "I reverse engineered container tooling to use a chroot". But a lot of people could elaborate more on why that's a bad idea.