-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman doesn't pull images on nomad job schedule #90
Comments
@ecky-l can you add a few more details please? What's your podman version, plugin version? Does the (debug) log reveal something useful? |
Sure:
Plugin Version is
Below is an extensive debug log of the nomad client whe I try to start the job with no image present.
|
IC The problem is related to a API handling bug in podman 2.x which should be fixed in podman 3.x via containers/podman@3fa61f0 But we're not ready to run the plugin against podman 3.x because of other regressions, see #89 I added a workaround in our non-hashicorp repo via pascomnet@8fd1872 and did not PR it back to hashicorp because of the upcoming podman 3.x release. A somewhat related PR is #88 and i will enhance it with the API workaround, soon. Thank you for the report. |
Thanks for the info. For me this means I would need to wait for podman 3.x to arrive in coreos. And hope that the API has a little more stabilized until then. I'll use docker in the mean time... |
@ecky-l : IMHO you can "mitigate the one bug by exploiting the other" if you want. |
@ecky-l your problem should be fixed. Can you check with recent podman version and a build from main branch? |
Hi,
I have a fresh podman installation on fedora coreos, with no local images. plugin is correctly configured and I try to run the example.nomad job (which is generated by
nomad job init
) with minor modifications:When running
nomad job run example.nomad
, the job is schedued but fails to start. But it starts when I runpodman pull docker.io/library/redis:4.0
on the nomad host. So apparently the image is not automatically pulled if it doesn't exist.Is this a misconfiguration on my side or a bug?
The text was updated successfully, but these errors were encountered: