Comment by chrisweekly 2 months ago Or put it in a microvm using eg smolmachines. 4 comments chrisweekly Reply causal 2 months ago I've never used smolmachines but I'm curious; why this over a container? apitman 2 months ago Containers are not security boundaries. Vulnerabilities in containers are much more common than in VMs. chrisweekly 2 months ago Kernel-level isolation is a significant security differentiator, for starters.https://github.com/smol-machines/smolvm#comparisonshows a good comparison table. bionade24 2 months ago Using runsc instead of runsc means that there's a hypervisor layer (gvisor, probably) in-between the kernel and the container userland
causal 2 months ago I've never used smolmachines but I'm curious; why this over a container? apitman 2 months ago Containers are not security boundaries. Vulnerabilities in containers are much more common than in VMs. chrisweekly 2 months ago Kernel-level isolation is a significant security differentiator, for starters.https://github.com/smol-machines/smolvm#comparisonshows a good comparison table.
apitman 2 months ago Containers are not security boundaries. Vulnerabilities in containers are much more common than in VMs.
chrisweekly 2 months ago Kernel-level isolation is a significant security differentiator, for starters.https://github.com/smol-machines/smolvm#comparisonshows a good comparison table.
bionade24 2 months ago Using runsc instead of runsc means that there's a hypervisor layer (gvisor, probably) in-between the kernel and the container userland
I've never used smolmachines but I'm curious; why this over a container?
Containers are not security boundaries. Vulnerabilities in containers are much more common than in VMs.
Kernel-level isolation is a significant security differentiator, for starters.
https://github.com/smol-machines/smolvm#comparison
shows a good comparison table.
Using runsc instead of runsc means that there's a hypervisor layer (gvisor, probably) in-between the kernel and the container userland