Just need Factorio integration. Given output from k describe pods -A, generate a blueprint with ingress represented by a belt balancer/splitter bit that feeds into furnaces leading to assemblers leading into boxes representing storage or something.
It’s not virtualization, it’s namespaces. Docker makes use of Linux kernel features; started out with cgroups and now uses libcontainer. Each container is running in its own isolated(ish) namespace on the same host kernel.
It’s _very_ different technology than virtualization.
You don’t need docker to make a container on Linux (or Solaris for that matter).
You are incorrect, this is OS-level virtualization:
"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].
>it’s namespaces. Docker makes use of Linux kernel features; started out with cgroups and now uses libcontainer. Each container is running in its own isolated(ish) namespace on the same host kernel.
Yes, OS-level virtualization.
>It’s _very_ different technology than virtualization.
Incorrect, this is a virtualization technology.
>You don’t need docker to make a container on Linux (or Solaris for that matter).
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..."
It’s not terribly difficult to get a gov domain, it’s just much easier to do an ordinary one. Smaller towns and cities outsource to cheap WYSIWYG type builders that also include a domain so it’s really simple to just go that route too.
It can get quite unprofessional at that level. There was a small suburb in our metro whose .com domain was an insult against the core city. I'm sure they thought it was funny but eventually it did get changed to the town and state name.
The OPs main point was that the existence of sideloading or third-party app stores hasn't led to major security issues. And apps still have to comply with the sandboxing.
