Live data from Hacker News

Barco: Linux Containers from Scratch in C

github.com

1–10 of 75 posts

Re: Barco: Linux Containers from Scratch in C

#7
> barco enforces a minimal set of restrictions to run untrusted code, which is not recommended for production use, where a more robust solution should be used.

Aren't containers never suitable for running untrusted code? You need AppArmor, bwrap, or similar AFAIK.

Re: Barco: Linux Containers from Scratch in C

#8
post #7

> barco enforces a minimal set of restrictions to run untrusted code, which is not recommended for production use, where a more robust solution should be used. Aren't containers never suitable for running untrusted code? You need AppArmor, bwrap, or similar AFAIK.

I would probably point at a virtual machine for a convenient place to run untrusted code. It's not perfect -- there are VM escapes -- but it's more convenient than a dedicated, air-gapped machine.

Re: Barco: Linux Containers from Scratch in C

#9
post #8
post #7

> barco enforces a minimal set of restrictions to run untrusted code, which is not recommended for production use, where a more robust solution should be used. Aren't containers never suitable for running untrusted code? You need AppArmor, bwrap, or similar AFAIK.

I would probably point at a virtual machine for a convenient place to run untrusted code. It's not perfect -- there are VM escapes -- but it's more convenient than a dedicated, air-gapped machine.

GKE runs every kubelet in its own gvisor-like userspace hypervisor.

https://cloud.google.com/blog/products/containers-kubernetes...

Re: Barco: Linux Containers from Scratch in C

#10
post #4

[flagged]

Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.

GP was asking if it could cause an issue for the OP, not complaining about an annoyance. It's something that the OP may want to address.
Post reply on HN