Any plans to support podman 3.0.0

[chris-rock]

Podman 3.0.0 has just landed and I was wondering if nomad is going to support the latest version?

[towe75]

Hi @chris-rock , thank you for reaching out.

Tests with podman 3.0 rc where successful and but it seems that a last minute API change is a show-stopper. See containers/podman#9351

Also there are various ubuntu related setup/upgrade problems which is worse given the fact that only 3.0 is available in their repository, see containers/podman#9358 . For now we're waiting for a point release to see if it improves the API situation. Otherwise we can, of course, react with some version checking and if/else API adapters.

[chris-rock]

Thank you for the quick feedback. I using alpine edge and it already ships the latest podman 3 as a package.

[matejvasek]

@chris-rock @towe75 The incompatible change was introduced accidentally. It should be fixed in v3.0.1.

[towe75]

@matejvasek : thank you for keeping us posted!

[chris-rock]

That is great. Thank you @matejvasek @towe75 Once podman 3.0.1 is alpine, I am going to do another try...

[towe75]

@matejvasek : 3.0.1 is out and i checked if our plugin "just works". I can see that the podman gh issue is resolved but it's a long, convoluted thread and i can not see if the API request works now as planed.

Fact is that i still have to adopt our codebase. We're using "/v1.0.0/libpod/containers/%s/wait?condition=%s" but only "/v1.0.0/libpod/containers/%s/wait?condition[]=%s" (note the brackets!) seems to do the job. Should i open another issue or is it what you want to do in this API? It's a bit annoying to add the brackets even if i only wait on one state.

[matejvasek]

@towe75 hmm, let me check, I tried it with something like http://127.0.0.1:1234/v1.0.0/libpod/containers/festive_poitras/wait?condition=running and it worked.

[matejvasek]

the brackets break functionality for me: http://127.0.0.1:1234/v1.0.0/libpod/containers/festive_poitras/wait?condition[]=running immediately returns on non running container.

[matejvasek]

how did you figure to put it there, I mean brackets?

[matejvasek]

I think that condition[] is discarded == it waits for default condition which is stopped.

[matejvasek]

I see only call is err = c.ContainerWait(timeout, name, "running") right?

[towe75]

@matejvasek : my bad, sorry. I ran into a combination of:

• earlier failed tests due to broken API in 3.0.0
• a automated build failed with 3.0.1 but on a different test (did not compare it before this post, sorry)
• a misinterpretation of your API spec. It says "Array of string" and my somewhat ancient PHP background translated this to ?condition[] and i gave it a try
• condition[] returns immediately which, in turn, lets my flaky test pass

I will improve the unit test and recheck. Thank you again for checking! 🍻