5 ms·

This is not a docker bug, it is a kernel bug. It could be triggered by other complex applications that use kernel container features.

• jacquesm 4y ago
  That pretty much makes the GPs point: emergent behavior arising from complexity.
• atoav 4y ago
  Or it could not be triggered if you don't use containers.
  • Fnoord 4y ago
    Would it have occurred on Podman as well?
    • markstos 4y ago
      Some of my servers were running Ubuntu with systemd+podman to manage services, and none of them had a problem.
      • remram 4y 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.
    • remram 4y ago
      Depending on your configuration. You would need to be using overlayfs with Podman.
  • kuschku 4y ago
    It could also be triggered by application sandboxing solutions that aren't containers.
    • vbezhenar 4y ago
      That's another reason to avoid those appimages and snaps.