Valentin BRICE

I believe you might have the same issue as #1294, changing your filter to `"docker-ce (>= 5:25.0.2)"` will produce instead : ``` docker-ce_5:26.1.4-1~debian.11~bullseye_amd64 docker-ce_5:26.1.3-1~debian.11~bullseye_amd64 docker-ce_5:26.1.2-1~debian.11~bullseye_amd64 docker-ce_5:26.1.1-1~debian.11~bullseye_amd64 docker-ce_5:26.1.0-1~debian.11~bullseye_amd64 docker-ce_5:26.0.2-1~debian.11~bullseye_amd64 docker-ce_5:26.0.1-1~debian.11~bullseye_amd64 docker-ce_5:26.0.0-1~debian.11~bullseye_amd64...

I'll be taking your feedback into account to find the least-cost path while protecting py-libzfs for async. If this is something that interest you, I would be happy to share...

I tried to reproduce your error, I believe your filter is the issue. On `containerd.io`, `docker-buildx-plugin` and `docker-compose-plugin` the packages are named straightforwardly upstream leading to filter being valid. However...