Y
Hacker News
new
|
ask
|
show
|
jobs
by
lixtra
1438 days ago
This is not a docker bug, it is a kernel bug.
It could be triggered by other complex applications that use kernel container features.
2 comments
atoav
1438 days ago
Or it could not be triggered if you don't use containers.
link
kuschku
1438 days ago
It could also be triggered by application sandboxing solutions that aren't containers.
link
vbezhenar
1438 days ago
That's another reason to avoid those appimages and snaps.
link
Fnoord
1438 days ago
Would it have occurred on Podman as well?
link
markstos
1438 days ago
Some of my servers were running Ubuntu with systemd+podman to manage services, and none of them had a problem.
link
remram
1438 days ago
You would have to be running this specific kernel version and one of your containers has to memory-map a file (not from a volume?), from what I understand.
link
remram
1438 days ago
Depending on your configuration. You would need to be using overlayfs with Podman.
link
jacquesm
1438 days ago
That pretty much makes the GPs point: emergent behavior arising from complexity.
link