> * Make --new-chroot default. Did you tested it? Do you have cases when it > does not work? Please report it. I plan to > keep --old-chroot option for some time (definitely for this year). > I welcome any comments.
I'm glad to see systemd-nspawn as new tool for containerization (+namespaces). It is really cool now, and I almost can use mock as light-weight containers for my tasks and builds. I didn't test `--new-chroot` itself because it doesn't fit my use-cases. How do you use `--new-chroot` ? I'm using `--shell` for some general purposes because it splits stdout and stderr of command, which is desired and expected behaviour. For example: $ mock -q -r epel7.cfg --shell 'rpmspec -P somespec.spec' > spec-parsed.spec , or `rpmspec -q ` and so on. rpmspec will output smth like > warning: bogus date in %changelog: Thu May 26 2006 Tim Waugh > <[email protected]> 3.1-13 on most of specs to stderr. But in case of --*-chroot or systemd-nspawn I'll get broken spec with mixed output and so on. It looks for me as systemd's bug now, not mock's. Isn't it? I tested systemd-nspawn a bit and faces with several issues. --- First of all, I can't mount_bind to /tmp inside chroot. It looks odd.. (I'll report it on BZ tomorrow). try config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/home', '/tmp/test' )) config_opts['use_nspawn'] = True In case of `use_nspawn` - /tmp instide chroot empty at all! --- Second - using of `use_nspawn` breaks `--shell` option also :( It mixes stderr and stdout. Does it hard to fix..? Would 'Make --new-chroot default' affect `--shell` behaviour ? --- Third. I faced with a bit strange behaviour while mock processing changes in config files. When I change * config_opts['macros']['%_smp_mflags'] * config_opts['chroot_setup_cmd'] * config_opts['plugin_conf']['root_cache_enable'] and so on, I expect that changes would be affected immediately and cache would be rebuilded. But it doesn't have any effects until I manually run # rm -rf /var/lib/mock* /var/cache/mock/* Is it "by design"..? Is it possible to force root rebuilding on changes that would affect build process..? --- Miroslav, do you have any plans/PoC on implementing templates ( https://github.com/rpm-software-management/mock/issues/6#issuecomment-262604060 ) ? :) _______________________________________________ buildsys mailing list -- [email protected] To unsubscribe send an email to [email protected]
