On Monday, 25 January 2021 10:47:25 PM AEDT Reinhard Tartler wrote:
> It seems that https://packages.qa.debian.org/n/nomad-driver-podman.html
> has never made it to testing, which makes me wonder whether
> it'll make it to bullseye.
Nothing should stop it from getting to "testing". It was blocked on
due to "autopkgtest-pkg-go" which is useless for binary-only packages.
At a time I did not mind because I was not sure whether it is
good enough for "testing".
the package won't migrate because of unsatisfiable dependencies on mips64el
and mips64el. This is because the 'podman' package doesn't (currently)
build on mipsen, whereas the nomad-driver-podman does. Apparently "britney"
doesn't permit "partial" migrations...
A low-effort workaround could be to add a build-dependency on podman to prevent
it from building on mipsen. A better fix could be to patch podman to build on
mipsen...
> Luckily it seems that issue
> has been fixed in latest master of nomad-driver-podman, cf.
No it hasn't... :( There is a serious regression:
https://github.com/hashicorp/nomad-driver-podman/issues/69
I'm having a hard time considering this a "serious" regression. The problem
as far as I understand is that while the driver does work fine with the new
REST interface, it doesn't allow you to upload images in OCI format from local
disk. If you instead chose to have imaged pulled from a (local) image registry,
the driver would work fine.
Blocking podman 3.0 because of this is something I can't get behind. But maybe
I'm missing something else here?