Description of problem: Fedora (and RHEL 8 beta) systems have following errors with dnf immediately. Version-Release number of selected component (if applicable): Fedora release 29 (Twenty Nine) How reproducible: Very Steps to Reproduce: 1. Take Fedora (or RHEL 8 Beta) container image, export it as tar and gzip # podman pull registry.fedoraproject.org/fedora # podman run -it fedora sleep 999999 # podman ps CONTAINER ID <ContainID> # podman export <ContainID> -o fedora.tar # podman kill <ContainID> 2. Use https://github.com/DDoSolitary/LxRunOffline on Windows C:\Temp>LxRunOffline-v3.3.2\LxRunOffline.exe install -n Fedora -d Fedora -f fedora.tar.gz C:\Temp>LxRunOffline-v3.3.2\LxRunOffline.exe set-default -n Fedora C:\Temp>LxRunOffline-v3.3.2\LxRunOffline.exe get-default Fedora 3. Run rpm or dnf command Actual results: [root@win10 Temp]# rpm -qa error: db5 error(12) from dbenv->open: Cannot allocate memory error: db5 error(22) from dbenv->close: Invalid argument error: cannot open Packages index using db5 - Cannot allocate memory (12) error: cannot open Packages database in /var/lib/rpm error: db5 error(12) from dbenv->open: Cannot allocate memory error: db5 error(22) from dbenv->close: Invalid argument error: cannot open Packages index using db5 - Cannot allocate memory (12) error: cannot open Packages database in /var/lib/rpm Expected results: Should not be RPM issues Additional info: WSL info @ https://docs.microsoft.com/en-us/windows/wsl/install-win10
Some public discussion going on at: https://github.com/Microsoft/WSL/issues/90 https://github.com/Microsoft/WSL/issues/3742
If mmap() would fail with EINVAL or such we could deal with it, but as long as WSL is pretending all is well we can't help. There are several tickets on WSL reporting how Berkeley DB and LMDB are broken because of mmap() issues, eg https://github.com/Microsoft/WSL/issues/3451 and https://github.com/Microsoft/WSL/issues/658 A bug in WSL can only be fixed in WSL.