containers/podman

`podman play kube` - Need Container Name as well as ID when Container Fails to Start

クローズ

#27,196 opened on 2025/09/30

 (9 件のコメント) (0 件のリアクション) (1 人の担当者)Go (3,107 件のフォーク)batch import
ContribfestGood First Issuekind/featurestale-issuetriagedvolunteers-wanted

Repository metrics

Stars
 (31,686 個のスター)
PR merge metrics
 (30d に merged PR はありません)

説明

Issue Description

I have seen problems like this a few times:

$ podman play kube --replace 'Some Project k8s.yaml'
Pods stopped:
Pods removed:
Secrets removed:
Volumes removed:
Pod:
6af8a146793983ef3ae16c36d606337d90c88a446643b59a4fe1dad060b5da51
Containers:
788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5
c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423

starting container bbb8d5fcc9584f5c2ce594bd368d564d76b8791008dbdea6217a2b9cd95f0ea2: runc: runc create failed: invalid rootfs: not an absolute path, or a symlink: OCI runtime error
starting container 788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5: a dependency of container 788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5 failed to start: container state improper
starting container c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423: a dependency of container c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423 failed to start: container state improper

Error: failed to start 3 containers

Here, I'm not concerned about what is causing the issue with starting the pod. However, only the container ID is printed, which obviously changes each time I redeploy. If the container can't be created, I can't look up the ID with podman ps - making it difficult to try and narrow down what the issue is - I have to start commenting and uncommenting lines in the YAML. I'd like ot see the container name from the k8s YAML printed also:

$ podman play kube --replace 'Some Project k8s.yaml'
Pods stopped:
Pods removed:
Secrets removed:
Volumes removed:
Pod:
hello-world-pod           (6af8a146793983ef3ae16c36d606337d90c88a446643b59a4fe1dad060b5da51)
Containers:
hello-world-pod-postgres  (788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5)
hello-world-pod-redis     (c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423)

starting container hello-world-pod-server (bbb8d5fcc9584f5c2ce594bd368d564d76b8791008dbdea6217a2b9cd95f0ea2): runc: runc create failed: invalid rootfs: not an absolute path, or a symlink: OCI runtime error
starting container hello-world-pod-postgres (788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5): a dependency of container hello-world-pod-postgres (788af1bb4db51250cbd14c05179db989810ded1613a6f7725f8bb768cd3d48e5) failed to start: container state improper
starting container hello-world-pod-redis (c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423): a dependency of container hello-world-pod-redis (c15e7890303a4806047b1b68585f6d80c9182867a27f8b0986fef74f8e052423) failed to start: container state improper

Error: failed to start 3 containers

Thanks!

Steps to reproduce the issue

See above

Describe the results you received

See above

Describe the results you expected

See above

podman info output

podman version
Client:       Podman Engine
Version:      5.5.2
API Version:  5.5.2
Go Version:   go1.24.4
Built:        Wed Jun 25 05:50:07 2025
OS/Arch:      linux/amd64

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

No

Additional environment details

No response

Additional information

No response

コントリビューターガイド