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: Network interface lost after exiting from an attached container #130031

Open
mz-pdm opened this issue Jul 12, 2021 · 2 comments
Open

podman: Network interface lost after exiting from an attached container #130031

mz-pdm opened this issue Jul 12, 2021 · 2 comments
Labels
0.kind: bug 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md

Comments

@mz-pdm
Copy link

mz-pdm commented Jul 12, 2021

Describe the bug

When I start a Podman container and attach to it, then exit the container and start it again, its non-loopback network interface is no longer present. When I start and stop the container without attaching to it the network interface is present after the next start, even if it was previously lost.

To Reproduce
Steps to reproduce the behavior:

  1. Run a Podman container and attach to it, e.g.: podman run -it --name test debian.
  2. Check the network interfaces: ip link. lo and tap0 are present.
  3. Run exit.
  4. Start the container again without attaching to it: podman start test.
  5. Check the network interfaces: podman exec test ip link. Only lo is present.
  6. Restart the container: podman stop test; podman start test (note that podman restart may exhibit a similar problem with older versions due to another Podman bug).
  7. Check again: podman exec test ip link. Both lo and tap0 are present again.

Expected behavior
In step 5. above, tap0 interface is present.

Additional context
The problem is present in both 21.05 and unstable.
I'm reporting this issue on NixOS rather than on Podman because I couldn't reproduce it on other distributions.

Notify maintainers
@marsam @adisbladis @saschagrunert @vdemeester @zowoq

Metadata

  • system: "x86_64-linux"
  • host os: Linux 5.10.48, NixOS, 21.05.1408.9376bf7b342 (Okapi)
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.3.12
  • channels(root): "nixos-21.05.1408.9376bf7b342, nixos-unstable-21.11pre301414.45fc7d4a35c"
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
@saschagrunert
Copy link
Member

I think that's an issue with the network handling in the rootless (slirp) case. We probably should move this topic to the Podman repository: https://github.com/containers/podman/issues/new

@stale
Copy link

stale bot commented May 1, 2022

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label May 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
Projects
None yet
Development

No branches or pull requests

2 participants