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

Real container state lost across reboot #1703

Closed
cjeanner opened this issue Oct 23, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@cjeanner
Copy link

commented Oct 23, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

[//]: # Uncomment only one, leave it on its own line:

kind bug

[//]: # kind feature

Description

Steps to reproduce the issue:

  1. Run a container that fails starting properly. It should be listed with an "Exited (non-0)" in podman ps --all

  2. Reboot the computer/server

Describe the results you received:
After the reboot, podman ps --all shows the container as "Created"

Describe the results you expected:
It should keep the "Exited (error-code)" instead, in order to stay consistent.

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

Output of podman version:

podman version 0.9.4-dev

Output of podman info:

host:
  BuildahVersion: 1.4-dev
  Conmon:
    package: podman-0.9.3.1-3.gita3c4ce6.el7.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.11.4, commit: 88d5276957861dea88b85f1d3f786612042cb4dd-dirty'
  Distribution:
    distribution: '"centos"'
    version: "7"
  MemFree: 8404660224
  MemTotal: 15871639552
  OCIRuntime:
    package: runc-1.0.0-54.dev.git2abd837.el7.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 6
  hostname: undercloud.lain.internux.ch
  kernel: 3.10.0-862.14.4.el7.x86_64
  os: linux
  uptime: 10m 3.02s
insecure registries:
  registries:
  - 192.168.24.1:8787
  - 192.168.24.3:8787
registries:
  registries:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ContainerStore:
    number: 90
  GraphDriverName: overlay
  GraphOptions:
  - overlay.override_kernel_check=true
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
  ImageStore:
    number: 37
  RunRoot: /var/run/containers/storage

Additional environment details (AWS, VirtualBox, physical, etc.):
Running on a libvirt domain - although this shouldn't affect the state reported by podman.

@TomSweeneyRedHat

This comment has been minimized.

Copy link
Collaborator

commented Oct 23, 2018

@cjeanner thanks for the problem report. Do you by chance have a Dockerfile or a recommended way to create a container that fails to start?

@cjeanner

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

Hello @TomasTomecek
I guess a command as "exit 1" in the Dockerfile should do the trick. I can confirm that in about an hour if you want - I have some running tests I can't really stop right now, and a bit out of resources :/

Cheers,
C.

@mheon

This comment has been minimized.

Copy link
Collaborator

commented Oct 23, 2018

@mheon mheon added the bug label Oct 23, 2018

@rhatdan

This comment has been minimized.

Copy link
Member

commented Dec 22, 2018

@mheon Has this been fixed?

@mheon

This comment has been minimized.

Copy link
Collaborator

commented Dec 22, 2018

Nope. I'll take it, should be a quick fix.

@cjeanner

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

@mheon I guess we can close this issue now since you merged #2273 ?

@mheon

This comment has been minimized.

Copy link
Collaborator

commented Feb 12, 2019

Yes. Good call.

@mheon mheon closed this Feb 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.