Closed rdbisme closed 9 months ago
That's weird; is this the only unusual behavior you're seeing?
(My best guess is something misinterpreting a seccomp denial as "no space left" but that seems odd -- however, you'd probably also be seeing issues with apt-get update
in that case :thinking:)
If it is seccomp related, then see https://github.com/docker-library/python/issues/837#issuecomment-1599640563.
If it is seccomp related, then see #837 (comment).
Can you reproduce the failure if you run the container with --security-opt seccomp=unconfined
? If it does not reproduce, then it is libseccomp
related and the two solutions are to either update Docker
& libseccomp
& runc
or to use the -bullseye
images.
@yosifkit Thanks for your reply. I'm having the problems on Gitlab runners, so no much control on how docker runs stuff. But I could try to update it and see if still reproduces.
Unfortunately, without a solid/minimal reproducer there's not much more we can do here (so I'm going to close). :bow:
I can confirm that updating libseccomp
on our machines fixed the problem :)
I'm not 100% sure this is related to the image update, but do you know if there's something that has changed in
bookworm
that could lead toTMPDIR
filling up much more than inbullseye
when pip installing?(I'm using
pipx
):