That isn't even true, you share your host kernel. There are parts of the kernel that aren't namespaced as well. The kernel keyring is probably the big one.
"OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..."[0].
>you share your host kernel
Kernel != OS
>There are parts of the kernel that aren't namespaced as well. The kernel keyring is probably the big one.
You can call it what you want but absolutely no one considers chroot virtualization in any meaningful sense. Nothing is being virtualized, containers are just regular processes on the host system.
1st of all yes, many people consider not only chroot to be virtualization (of the file system). Yes it is arguable as it is the birth of lightweight virtualization. But you were wrong in saying no one does.
>but absolutely no one considers chroot virtualization in any meaningful sense.
Absolutely everyone who's knowledgable in virtualization considers chroot to be a type of OS-level virtualization.
>Nothing is being virtualized, containers are just regular processes on the host system.
Wrong, "...OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances..."
You are incorrect, this is true:
"OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..."[0].
>you share your host kernel
Kernel != OS
>There are parts of the kernel that aren't namespaced as well. The kernel keyring is probably the big one.
Immaterial.
[0] https://en.m.wikipedia.org/wiki/OS-level_virtualization