Alexei Ledenev

Try running the following command: ``` DOCKER_BUILDKIT=1 docker build -t pumba -f docker/Dockerfile --build-arg TARGETOS=linux --build-arg TARGETARCH=amd64 . ```

I'm working on containerd support. Once it's completed will check podman

@rantidev please provide more details about your runtime environment: OS, docker host, version, where you run pumba and target containers, etc. - everything that will help to reproduce the issue....

@toky0 thank you. I will try to reproduce in a similar environment

Not yet. I think it's related to Linux distribution you are using and the cgroups package. Can you try to run it on Ubuntu or Redhat LTS version?

This can happen when a new node is attached to a GKE cluster for whatever reason: node upgrade, scale-up, health restart, etc. In this case, node info is updated with...

#138 fixes this issue too Tested with: - manual delete node - static address released and new node added taking released address - cluster resize - resize cluster (scale up...

@Tchirana thank you for reporting Need to implement distributed Mutex, planned in the future. Currently added a random 10s-max sleep before listing available IP addresses. Supposed to reduce conflicts a...

fixed

@sephethus please check the full [example](https://gist.githubusercontent.com/alexei-led/6ae6d57ed08b26c64f534f87fc1872df/raw/8c479c02b77f14a4b8796b18000b4f8636b14d9f/Markdium-YAML.yaml) The valid flow is the following: 1. create a new `emptyDir` volume in a Pod, call it `secrets-init-volume` for example 2. add a `secrets-init`...