Skip to content
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 'play kube' fails when editing libpod.conf #3533

Closed
jttrail0 opened this issue Jul 9, 2019 · 4 comments
Closed

podman 'play kube' fails when editing libpod.conf #3533

jttrail0 opened this issue Jul 9, 2019 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@jttrail0
Copy link

jttrail0 commented Jul 9, 2019

When modifying the "infra_image" variable set in /usr/share/containers/libpod.conf running "podman play kube mypod.yaml" returns "Error: pod was given but no pod is specified: invalid argument"

/kind bug

Description

I need to modify the infra container used because the host does not have internet access. When I return the libpod.conf back to the original value the command runs, but returns an error because "k8s.gcr.io/pause:3.1" cannot be pulled nor can it be pinged. (Sorry for the general description I cannot copy and paste directly from the environment I am describing but I'm assuming this is known because the default pause container cannot be pulled).

The image I am replacing was pulled and loaded so the registry is localhost/kubernetes/pause:go.

I have seen hints of some podman play kube commands being fixed in 1.4 in issues... is this issue solved as well. It is a must to test pods in an environment that does not have open internet access and requires effort/time to pull in external containers.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

podman version 1.3.2
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 9, 2019
@mheon
Copy link
Member

mheon commented Jul 9, 2019

Fixed upstream already - dupe of #3157

@mheon
Copy link
Member

mheon commented Jul 9, 2019

We're shipping a 1.4.x release in 7.6.6 which should resolve this.

@jttrail0
Copy link
Author

jttrail0 commented Jul 9, 2019

thanks!

@haircommander
Copy link
Collaborator

closing this because it's fixed upstream. Please re-open if you disagree @jttrail0

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

4 participants