Arnaud Rebillout

I'm having the same issue. I noticed a change in the behavior of docker-py between version 4.2 and 4.3, caused by 727080b3cca846a28d5436bed861359c9742c7e1 Before this change, the client was created with...

I did more research on that one, at https://gitlab.com/kalilinux/build-scripts/kali-vm/-/issues/25#note_1290346720. From what I can see, the issue is not in the `.ovf`, it's in the `.vmdk`. If it's created with vmware...

Which one? The 404 counter?

I propose to disable line wrapping, without switching to yaml.v3, with this patch: https://github.com/etix/mirrorbits/pull/154

Alternatively, let's just bump the gopkg.in/yaml dependency to v3: https://github.com/etix/mirrorbits/pull/163

Note that there's package in Debian (unstable/testing only). It's built for all architectures: https://buildd.debian.org/status/package.php?p=mirrorbits

Debian user reported that indeed, he can't use docker on a machine where a nftables-based firewall is enabled: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921600

I found a Debian ticket with a similar need, but different approach: https://bugs.debian.org/889552 In this ticket, Paul suggests to ignore processes that are too young. That would also work for...

Hello! Yes, ignoring containers by name patterns would help. Our disposable lxc containers are named `ci-017-222a371c` for example, so I would be happy if I could ignore containers named `^ci-.*`.

Looks good, thank you!