Hello Stef, Stef Walter [2017-01-04 16:56 +0100]: > This is pretty cool. And the experience has gotten you familiar with all > sorts of details already.
Right, that's mostly why I went the manual route, for the learning exercise; and TBH I'm also a bit of a control freak, I don't like libvirt or vagrant much: they sloppily copy huge images around in triplicate, it's not obvious which things are running (e. g. "virsh list" doesn't show vagrant VMs) or how to clean up behind them, they try to be too magic for my taste (but then e. g. its promised folder sync doesn't work with the libvirt/qemu provider), and it's relying on some third-party images. > My question is whether you've tried 'vagrant up' in a cockpit git checkout > ... and whether that solves the same issue ... or is hopelessly broken :D I've tried vagrant by itself and quickly ran into some issues, so TBH I didn't try it with cockpit yet -- but doing that is still on my list. It would certainly be a more "standard" way to create dev VMs, so I want to give it a proper shot. The currently specified RAM size can't possibly have worked anytime recent for running the tests (it needs about 6 GiB RAM, 1 GiB will fall over really fast), lacks all of the build/test deps, and uses F24, so I guess this has only been used to run cockpit itself, not for running any of its tests? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) _______________________________________________ cockpit-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
