Description of problem: A new default has been added to mock to use nspawn, while this might be a awesome idea, it seems to be wreaking havoc on my ability to built Mageia packages in Docker. A Simple solution would be to turn it off. However I am not sure what it brings to the table, and maybe I'm just a corner case. Version-Release number of selected component (if applicable): mock-1.4.2-1 How reproducible: Everytime Steps to Reproduce: 1. Use mock in a Docker container 2. Try to rebuild src rpm.
Created attachment 9704 [details] patch for the issue The simple solution is to just add: "config_opts['use_nspawn'] = False" to the mock files as presented in the example patch.
CC: (none) => JMiahMan
CC: (none) => marja11Assignee: bugsquad => ngompa13
Nspawn containers basically do the same thing Docker does, so if you're using mock in Docker, you will want to pass "--old-chroot" to the command to revert to using the chroot() instead, which should work inside of Docker. Nspawn containers automatically namespace out everything, so you don't get collisions between different builds running at the same time, and it makes it far harder for host information to leak into the container and vice versa. I do not intend to change the default, as upstream has intended for nspawn to be used to enhance the security of building packages.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
That works, Thanks