-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
NetworkSettings missing when container is running in pod #8073
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
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
Categorizes issue or PR as related to a bug.
label
Oct 20, 2020
I'll take this one. |
mheon
added
the
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
label
Oct 20, 2020
mheon
added a commit
to mheon/libpod
that referenced
this issue
Oct 20, 2020
When a container either joins a pod that shares the network namespace or uses `--net=container:` to share the network namespace of another container, it does not have its own copy of the CNI results used to generate `podman inspect` output. As such, to inspect these containers, we should be going to the container we share the namespace with for network info. Fixes containers#8073 Signed-off-by: Matthew Heon <mheon@redhat.com>
Fixed by #8075 |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Oct 20, 2020
When a container either joins a pod that shares the network namespace or uses `--net=container:` to share the network namespace of another container, it does not have its own copy of the CNI results used to generate `podman inspect` output. As such, to inspect these containers, we should be going to the container we share the namespace with for network info. Fixes containers#8073 Signed-off-by: Matthew Heon <mheon@redhat.com>
cevich
pushed a commit
to cevich/podman
that referenced
this issue
Oct 22, 2020
When a container either joins a pod that shares the network namespace or uses `--net=container:` to share the network namespace of another container, it does not have its own copy of the CNI results used to generate `podman inspect` output. As such, to inspect these containers, we should be going to the container we share the namespace with for network info. Fixes containers#8073 Signed-off-by: Matthew Heon <mheon@redhat.com>
edsantiago
pushed a commit
to edsantiago/libpod
that referenced
this issue
Nov 4, 2020
When a container either joins a pod that shares the network namespace or uses `--net=container:` to share the network namespace of another container, it does not have its own copy of the CNI results used to generate `podman inspect` output. As such, to inspect these containers, we should be going to the container we share the namespace with for network info. Fixes containers#8073 Signed-off-by: Matthew Heon <mheon@redhat.com>
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 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
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.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When a container is started within a pod, network settings are empty. If started standalone, it works as expected.
Since pods share the network namespace across all containers in it, it should show the same settings as the infra container.
Steps to reproduce the issue:
podman pod create --name=test
podman run -d --pod=test alpine sleep 2000
podman inspect
Describe the results you received:
Inspect output when running in pod:
Describe the results you expected:
Inspect output when running "standalone":
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: