Is the "podman play kube" feature available in the version v1.0.0? #2209
Assignees
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
openshift-ci-robot
added
the
kind/bug
|
Try this on fedora 29, got the same result: 🤔 |
|
I will try your yaml today. Thanks for providing it! The play feature is also geared at playing yaml that podman generates using |
|
@baude I tryed the "podman generate kube" function, it works fine. But after run "podman play kube" to try to start with the yaml (after delete the origin container), it return the new error: "ERRO[0000] name nostalgicarchimedes is in use: container already exists". |
|
That is because the container you created the YAML from still exists under that same name (or the pod). You might also be interested in https://developers.redhat.com/blog/2019/01/29/podman-kubernetes-yaml/ |
|
If you delete the pod and the container does it work? |
|
Thank you for reply! Actually I deleted all the PODs and containers before running the "podman play kube". #2209 (comment), the result of "podman pod list" and "podman ps -a":
And I used to run according to the article (https://developers.redhat.com/blog/2019/01/29/podman-kubernetes-yaml/), everything is fine, so I have no idea now. |
|
Try this in a public env (https://www.katacoda.com/courses/kubernetes/launch-single-node-cluster) without kubernetes cluster (does not run the minikube start), got the same error. |
|
@warmchang is the yaml in ^^ generated by podman or not? |
|
|
@warmchang @baude Is this still an issue? |
|
@rhatdan we dont support running yaml that isnt generated by us. But I would really prefer that we dont panic. |
|
Ok, I am giving this to @haircommander to look at, I want to make your statement less true over time. |
baude
added a commit
to baude/podman
that referenced
this issue
Mar 8, 2019
if an input YAML file lacks securitycontext and working dir for a container, we need to be able to handle that. if no default for working dir is provided, we use a default of "/". fixes issue containers#2209 Signed-off-by: baude <bbaude@redhat.com>
|
the root cause was two fold here: the input lacks a security context for containers which we do output for generate kube. it is required for libpod container running. we can now handle not having that input. once that was fixed, the input file also didn't define a CWD which is also a libpod requirement. we can now tolerate both those and set a default cwd if not provided. i tested your YAML provided in the Jan 31 comment and it worked perfectly. |
muayyad-alsadi
pushed a commit
to muayyad-alsadi/libpod
that referenced
this issue
Apr 21, 2019
if an input YAML file lacks securitycontext and working dir for a container, we need to be able to handle that. if no default for working dir is provided, we use a default of "/". fixes issue containers#2209 Signed-off-by: baude <bbaude@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
There is an exciting feature in v1.0.0 release:
Added the podman play kube command to create pods and containers from Kubernetes pod YAML.
I can't help but want to try it, but there is an error. Is the way I use it wrong?
Steps to reproduce the issue:
Describe the results you received:
Return an error:
Check the result, and the POD just include the infra-container:
Describe the results you expected:
The POD running well without error.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info:Additional environment details (AWS, VirtualBox, physical, etc.):
The katacoda environment.
The text was updated successfully, but these errors were encountered: