[ailideex]

> A “container” is just a term people use to describe a combination of Linux namespaces and cgroups.

And those people should stop because that would be inaccurate. More specifically, a "container" can be any of the following:

- Someone who contains; something that contains. An item in which objects, materials or data can be stored or transported.

- (transport) A very large, typically metal, box used for transporting goods.

- (by extension) Someone who holds people in their seats or in a (reasonably) calm state.

- (computing) A file format that can hold various types of data.

- (object-oriented programming) An abstract data type whose instances are collections of other objects.

- (computing, graphical user interface) Any user interface component that can hold further (child) components.

...

If we are talking about a Docker Container (here Docker Container is a proper noun), on the other hand - then clearly you are still wrong - as Docker have worked at various times on Windows and FreeBSD.

Now trying to grasp at even more straws to find some the "container" definition of the gaps that may give some justification to your claims, we can look at the other proper noun "OCI Container" ... but alas ...

https://www.opencontainers.org/faq

> Will the runtime and image format specs support multiple platforms?

> Yes. For example, take a look at the runtime-specification configuration where it mentions example Linux, Windows and Solaris configurations. There are also multiple implementations of the runtime-specification that you can take a look at.

It seems then that you are just wrong. Plain and simple. I'm seriously concerned with whoever is having you interview candidates.