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

rootless: "podman run" gives an imperfect error message if subgid not configured correctly #2584

Closed
sysrich opened this issue Mar 8, 2019 · 3 comments
Assignees
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

@sysrich
Copy link
Contributor

sysrich commented Mar 8, 2019

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

/kind bug

Description

Scenario - /etc/subuid configured properly, but /etc/subgid not configured at all

User runs podman run hello-world and gets

ERRO[0000] error creating libpod runtime: Error running podman info while refreshing state: exit status 1

This is rather confusing and does not help the user debug what actually went wrong.
If the user does something different like podman image ls they get a more helpful error message

ERRO[0000] No subgid ranges found for group "ilmehtar" in /etc/subgid

I would expect podman run to give the same error message given the misconfiguration is the same for podman run as it is for podman image

Output of podman version:

Version:            1.1.2
RemoteAPI Version:  1
Go Version:         go1.11.5
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.11.5
  podman version: 1.1.2
host:
  BuildahVersion: 1.7.1
  Conmon:
    package: podman-1.1.2-3.1.x86_64
    path: /usr/lib/podman/bin/conmon
    version: 'conmon version 1.13.1, commit: '
  Distribution:
    distribution: '"opensuse-tumbleweed"'
    version: "20190301"
  MemFree: 11381452800
  MemTotal: 33540861952
  OCIRuntime:
    package: runc-1.0.0~rc6-3.1.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc6
      spec: 1.0.1-dev
  SwapFree: 34359734272
  SwapTotal: 34359734272
  arch: amd64
  cpus: 8
  hostname: iwreckit.suse.de
  kernel: 4.20.12-1-default
  os: linux
  rootless: true
  uptime: 94h 51m 26.89s (Approximately 3.92 days)
insecure registries:
  registries: []
registries:
  registries:
  - docker.io
store:
  ConfigFile: /home/ilmehtar/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: vfs
  GraphOptions: null
  GraphRoot: /home/ilmehtar/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 1
  RunRoot: /run/user/1000
  VolumePath: /home/ilmehtar/.local/share/containers/storage/volumes
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 8, 2019
@rhatdan
Copy link
Member

rhatdan commented Mar 8, 2019

@giuseppe @mheon Could you guys take a look?

@giuseppe
Copy link
Member

giuseppe commented Mar 8, 2019

@rhatdan this is the "podman info" error not being propagated to the caller. You were working on a patch for that, do you still have it?

giuseppe added a commit to giuseppe/libpod that referenced this issue Mar 8, 2019
we use "podman info" to reconfigure the runtime after a reboot, but we
don't propagate the error message back if something goes wrong.

Closes: containers#2584

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
@giuseppe
Copy link
Member

giuseppe commented Mar 8, 2019

PR here: #2588

giuseppe added a commit to giuseppe/libpod that referenced this issue Mar 8, 2019
we use "podman info" to reconfigure the runtime after a reboot, but we
don't propagate the error message back if something goes wrong.

Closes: containers#2584

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
muayyad-alsadi pushed a commit to muayyad-alsadi/libpod that referenced this issue Apr 21, 2019
we use "podman info" to reconfigure the runtime after a reboot, but we
don't propagate the error message back if something goes wrong.

Closes: containers#2584

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
@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 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Development

No branches or pull requests

5 participants