28
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Feb 2024
28 points (100.0% liked)
Cybersecurity
5632 readers
89 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 1 year ago
MODERATORS
What are runc, buildkit, moby and docker desktop? Are these tools part of a normal docker setup on linux?
Yes, the runc vulnerability affects both docker cli and podman cli.
Docker and Kubernetes use containerd, and Podman uses runc directly.
https://github.com/containerd/containerd/pull/9724
https://github.com/containers/podman/pull/21483
Do not run any untrusted images until the vulnerability is fixed, especially not as root.
Docker Desktop won't really affect you as a Linux user, but moby/buildkit serves as the basis for "docker build" when building docker images. Runc is one of the base packages used for the software and so this will affect nearly all users of Docker until it gets resolved.