If there is no /etc/nsswitch.conf file, podman crashes. This is because shadow_logfd is NULL on line 59: 55 // read nsswitch.conf to check for a line like: 56 // subid: files 57 nssfp = fopen(nsswitch_path, "r"); 58 if (!nssfp) { 59 fprintf(shadow_logfd, "Failed opening %s: %m", nsswitch_path); 60 atomic_store(&nss_init_completed, true); 61 return; 62 } Seen with shadow-utils-4.9-8.fc35.x86_64.
Can you provide the steps to reproduce the problem? I'm not a podman expert and so far I haven't been able to reproduce it. By the way, I think that upstream already solved this problem in https://github.com/shadow-maint/shadow/pull/474.
For me, “podman pull fedora” or “podman system reset” crash.
FEDORA-2022-8e62470e3e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e62470e3e
FEDORA-2022-8e62470e3e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8e62470e3e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e62470e3e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-8e62470e3e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.