Non-containerized applications. Not in a container. It’s not complicated. Running “on bare metal” sounds cool but it’s a wildly inaccurate description. Containerized applications run on the system natively just like non-containerized applications. So if one of them runs “on bare metal” then then others do as well.
But historically “on bare metal” is used for embedded or micro-controllers where you don’t have an OS.
Bare metal is commonly used to describe server OS installs that are not virtualized and are installed directly to the hardware. People are most likely conflating containerized and virtualized.
TBH its not the users fault, the documentation is always like (click here for docker install instructions, or if you don’t want docker click here for bare metal instructions) and the latter is just apt get and some config edits.
What are we supposed to call it? Genuine question
Non-containerized applications. Not in a container. It’s not complicated. Running “on bare metal” sounds cool but it’s a wildly inaccurate description. Containerized applications run on the system natively just like non-containerized applications. So if one of them runs “on bare metal” then then others do as well.
But historically “on bare metal” is used for embedded or micro-controllers where you don’t have an OS.
Bare metal is commonly used to describe server OS installs that are not virtualized and are installed directly to the hardware. People are most likely conflating containerized and virtualized.
Aye - that’s another reasonable use of the phrase.
TBH its not the users fault, the documentation is always like (click here for docker install instructions, or if you don’t want docker click here for bare metal instructions) and the latter is just apt get and some config edits.
Ugh really? I haven’t seen that myself but that’s frustrating.