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.

Sign up for GitHub

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

Jump to bottom

podman pod stop and podman pod start don't reopen ports to containers #7103

Closed
fp7 opened this issue Jul 28, 2020 · 2 comments
Closed

podman pod stop and podman pod start don't reopen ports to containers #7103

fp7 opened this issue Jul 28, 2020 · 2 comments
Assignees
@ashley-cui
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

@fp7
Copy link

fp7 commented Jul 28, 2020

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description
After podman pod restart <name> the containers will be still accessible from the host.
After podman pod stop <name>; podman pod start <name> they are not

Steps to reproduce the issue:

  1. podman pod create --name test -p "9200:9200"

  2. podman run -d --pod test -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:7.6.2

  3. podman pod stop test

  4. podman pod start test

  5. curl localhost:9200/_cat

Describe the results you received:
I get curl: (7) Failed to connect to localhost port 9200: Connection refused

Describe the results you expected:
I would expect the port to be reachable

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

Output of podman version:

Version:      2.0.3
API Version:  1
Go Version:   go1.14.4
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.15.0
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.18, commit: '
  cpus: 8
  distribution:
    distribution: ubuntu
    version: "18.04"
  eventLogger: file
  hostname: tp
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 4.15.0-112-generic
  linkmode: dynamic
  memFree: 16008376320
  memTotal: 41937190912
  ociRuntime:
    name: runc
    package: 'containerd.io: /usr/bin/runc'
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
      spec: 1.0.1-dev
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  rootless: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: 'slirp4netns: /usr/bin/slirp4netns'
    version: |-
      slirp4netns version 0.4.3
      commit: unknown
  swapFree: 1027600384
  swapTotal: 1027600384
  uptime: 3h 43m 26.34s (Approximately 0.12 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /home/finn/.config/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 2
    stopped: 0
  graphDriverName: vfs
  graphOptions: {}
  graphRoot: /home/finn/.local/share/containers/storage
  graphStatus: {}
  imageStore:
    number: 17
  runRoot: /run/user/1000/containers
  volumePath: /home/finn/.local/share/containers/storage/volumes
version:
  APIVersion: 1
  Built: 0
  BuiltTime: Thu Jan  1 01:00:00 1970
  GitCommit: ""
  GoVersion: go1.14.4
  OsArch: linux/amd64
  Version: 2.0.3

Package info (e.g. output of rpm -q podman or apt list podman):

Listing... Done
podman/unknown,now 2.0.3~1 amd64 [installed]

Additional environment details (AWS, VirtualBox, physical, etc.):
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 28, 2020
@rhatdan
Copy link
Member

rhatdan commented Jul 28, 2020

@ashley-cui PTAL

@ashley-cui ashley-cui mentioned this issue Aug 10, 2020
Merged
@Luap99 Luap99 mentioned this issue Aug 21, 2020
Closed
mheon added a commit to mheon/libpod that referenced this issue Aug 24, 2020
@mheon
Ensure pod infra containers have an exit command
484bd0a 
Most Libpod containers are made via `pkg/specgen/generate` which
includes code to generate an appropriate exit command which will
handle unmounting the container's storage, cleaning up the
container's network, etc. There is one notable exception: pod
infra containers, which are made entirely within Libpod and do
not touch pkg/specgen. As such, no cleanup process, network never
cleaned up, bad things can happen.

There is good news, though - it's not that difficult to add this,
and it's done in this PR. Generally speaking, we don't allow
passing options directly to the infra container at create time,
but we do (optionally) proxy a pre-approved set of options into
it when we create it. Add ExitCommand to these options, and set
it at time of pod creation using the same code we use to generate
exit commands for normal containers.

Fixes containers#7103

Signed-off-by: Matthew Heon <[email protected]>

<MH: Fixed cherry-pick conflicts>

Signed-off-by: Matthew Heon <[email protected]>
@duckie
Copy link

duckie commented Nov 1, 2020 •
edited
Loading

See #8211

@duckie duckie mentioned this issue Nov 1, 2020
Closed
ahwayakchih added a commit to ahwayakchih/nobbic that referenced this issue Dec 18, 2020
@ahwayakchih
fix: work around problem with ports not exposed in podman pod start
337f095 
After `podman pod stop X` and then `podman pod start X`, ports are not
responding to requests from host to guest.

containers/podman#7103
@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 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ashley-cui ashley-cui

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
Milestone
No milestone
Development

No branches or pull requests
5 participants
@duckie @rhatdan @fp7 @openshift-ci-robot @ashley-cui