this post was submitted on 10 Dec 2023
33 points (100.0% liked)

No Stupid Questions (Developer Edition)

921 readers
1 users here now

This is a place where you can ask any programming / topic related to the instance questions you want!

For a more general version of this concept check out [email protected]

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

I think from what I've read that this is the case, but I've read some other info that's made it less clear to me.

On the second part of the question regarding container engines, I'm pretty sure that may also be correct, and it kinda makes me wonder a little about risks of engine lock-in, but that may be a little out of scope.

you are viewing a single comment's thread
view the rest of the comments
[–] onlinepersona 13 points 10 months ago (1 children)

Containers are practically a linux thing. The specs to run containers are open (Open Container Initiative). That's why if you aren't on linux, the most common solution is to virtualise linux or add a layer that translates linux syscalls to those on the host OS (e.g windows subsystem for linux). Once the linux environment exists you have multiple orchestrators (docker, podman, kubernetes, etc.). They all either have their own runtime or use an existing one (runc, crun, youki, ...).

I haven't read the OCI specs, but IINM containers are built upon linux primitives (namespaces, cgroups, and I forget the rest).

[–] [email protected] 1 points 10 months ago (1 children)
[–] onlinepersona 1 points 10 months ago

Woah, that's news to me. Are these OCI containers?