Open oogali opened 6 years ago
I've faced with same issue and found solution with disabling spawn in config like this: echo "config_opts['use_nspawn'] = False" >> /etc/mock/site-defaults.cfg
It will be nice to describe this in docs in Docker section.
Yes, we don't know how to run systemd-nspawn in container, yet. See pull request #337 which should lower the pain. Otherwise this is known problem.
Since this is about making systemd-nspawn work in docker, I'm flagging it as RFE.
Short description of the problem
@xsuchy I have a similar issue to #96, if not the same issue, despite adding the
SYS_ADMIN
capabilitiy. However, I have not tried the--old-chroot
option that @shanemcd mentioned in that issue.Output of
rpm -q mock
Steps to reproduce issue
mock ... --init
Do not forget to mention full commandline with the mock command you executed.
Any additional notes
I'll jump to the core of the issue (rather than including several hundred lines of mock/yum installing packages).
And this is the Dockerfile I'm using to build my image:
The entrypoint is nothing fancy, just this: