Run containers from oci-archive and non standard image sources

[towe75]

It would be useful to run containers from images in oci-archive format.
We fixed this issue for varlink api in #67

But switching to podman api v2 introduces the same problem. This is related to containers/podman#6744

[onlyjob]

Looks like 0.2.0 was actually released with this regression... :(

CC: @drewbailey, @krishicks

[towe75]

@onlyjob : it was a misleading information in the changelog, #67 was fixed right before 0.2.0 release.
I knew that it would still be broken with http API - hence this ticket. I will handle it soon and this time it's covered with a unit test ;-)

[onlyjob]

I've backported fix to 0.1.0 and it works with Varlink. However yesterday I tried 0.2.0 and could not start any of my images...

Thank you for your care and attention for driver-podman.

[towe75]

We're blocked by containers/podman#8927

[towe75]

@onlyjob do you follow the podman issue? For now there is no way to use the http API to get it working. What is your opinion?

[onlyjob]

Yes, I'm following, thanks... Not upgrading is my only option, obviously... :( But that also means that we can't disable deprecated Varlink in Debian's Podman...

[pabloyoyoista]

@onlyjob, this has in principle been fixed in #101. There is a simple test which worked successfully and imports the right images from the archives. However, I did not do any real-world testing. If you are able to check it out, maybe there is a chance any further bugs appear or we can consider this as solved. Only oci-archive and docker-archive are currently allowed transports other than the default docker