Created attachment 1738416 [details] anaconda.log Description of problem: During the setup of SB, I wanted to customize my partitions to achieve the following: - /var/lib/containers on a different subvolume - /var/lib/libvirt on a different subvolume Both is not achievable, since the installer will stop with the below error: mount ['--bind', '/mnt/sysimage/var/lib/containers', '/mnt/sysroot/var/lib/containers'] exited with code 32 Since the docs state /var/* should be possible, I thought this should be possible. Version-Release number of selected component (if applicable): anaconda 33.25.4 How reproducible: Steps to Reproduce: 1. Start a machine with the fedora silverblue image 2. Choose custom disk 3. Generate defaults based on btrfs 4. add a subolume for /var/lib/containers 5. approve the creation of partitions 6. start installation Actual results: Installation stops with: mount ['--bind', '/mnt/sysimage/var/lib/containers', '/mnt/sysroot/var/lib/containers'] exited with code 32 Expected results: Installation is done and /var/lib/containers is created. Additional info: This is a requested report, based on: https://github.com/fedora-silverblue/issue-tracker/issues/114
Created attachment 1738417 [details] syslog
Created attachment 1738418 [details] storage.log
Created attachment 1738419 [details] sysinfo
I don't see the error in the logs. Could you please attach also 'program.log' that could reveal some more details.
Created attachment 1758804 [details] program.log
Hi Jiri, thank you for having a look. I reproduced the issue and attached the requested "program.log". I hope this helps. Best regards, Daniel
Seems like the problem is that the folder where we want to put your mount point does not exists. 11:29:52,335 INF program: Running... mount --bind /mnt/sysimage/var/lib/containers /mnt/sysroot/var/lib/containers 11:29:52,340 INF program: mount: /mnt/sysroot/var/lib/containers: mount point does not exist. 11:29:52,341 DBG program: Return code: 32
PR: https://github.com/rhinstaller/anaconda/pull/3297
*** Bug 1845095 has been marked as a duplicate of this bug. ***