Description of problem: After updating from podman-2.0.4-1.fc32.x86_64.rpm to podman-2.0.5-1.fc32 sudo in toolbox stopped suddenly started to ask for a password I don't have. Downgrading to podman-2.0.4-1.fc32.x86_64.rpm fixed this for me. Steps to Reproduce: 1. toolbox create 2. toolbox enter 3. sudo whoami Additional info: Toolbox also showed a new warning when entering a toolbox with 2.0.5 (vanishes with downgrading, too): /usr/bin/id: cannot find name for group ID 1000
The issue of sudo(8) asking for a password is fixed in Toolbox 0.0.95: * F33: https://bodhi.fedoraproject.org/updates/FEDORA-2020-885e55baff * F32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-306addaac0 Testing welcome. However, the issue of the warning about the missing group when entering a container is something that should be fixed in Podman (or at least that's my understanding): https://github.com/containers/podman/issues/7389
*** Bug 1874114 has been marked as a duplicate of this bug. ***
(In reply to Debarshi Ray from comment #1) > https://github.com/containers/podman/issues/7389 Fixed upstream. Will add to rpm once we have a new tag.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The fix has since been part of an RPM that was delivered to users. I can't recall the exact NEVRA of the build, though.