3 ms·

So is the container somehow tightly bound to the configuration / kernel of the machine it was built on? I seem to have some recollection that you have to run t

So is the container somehow tightly bound to the configuration / kernel of the machine it was built on? I seem to have some recollection that you have to run the container on a host with the same kernel or libraries or something like that which seemed like a real downside to me.

__d 5y ago
The container shares the actual kernel, but has independent namespaces (including mounted filesystems). In general, the precise kernel version doesn't matter to applications: libc will hide a wide range of stuff for you, and you bring your own libc in the container image (assuming you need it. This is not true for eg. Golang).