Re: Fedora for Web Development fail
On Tue, Oct 02, 2018 at 12:14:42PM -0400, Cole Robinson wrote: > Coming to this thread late. There's been an RFE for virt-manager for > a while to send in cloud-init data for cloud images: > https://bugzilla.redhat.com/show_bug.cgi?id=981693 Yes! I couldn't find it because ahem, I was convinced that I was the one who had filed it. :) -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
* Cole Robinson: > On 09/27/2018 03:26 PM, Florian Weimer wrote: >> * Adam Williamson: >> >>> I don't think we ship anything that is exactly a *disk image* for this >>> kind of non-cloud, non-Atomic, minimal, probably-virtual deployment, >>> aside from the ones intended for vagrant use. At least not for x86_64. >>> I suppose I'd tend to use virt-install or just install from the network >>> install image, for this kind of use. >> >> Maybe we should look at this backwards and try to implement an >> instance-data injection environment in libvirt, by default. Then it >> would be possible to use images which contain cloud-init unmodified, and >> safely. >> > > Coming to this thread late. There's been an RFE for virt-manager for a > while to send in cloud-init data for cloud images: > > https://bugzilla.redhat.com/show_bug.cgi?id=981693 > > That would require using libguestfs to detect that the disk image is a > ex. Fedora cloud image. And nowadays I'd lean more towards just > disabling cloud-init and setting an empty password instead of doing > the specific cloud-init dance. It's not trivial though. I think that running a web server that merely serves the intended SSH public key for the root account would not have to be disabled by libvirt for non-cloud images. That data isn't really secret. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On 09/27/2018 03:26 PM, Florian Weimer wrote: * Adam Williamson: I don't think we ship anything that is exactly a *disk image* for this kind of non-cloud, non-Atomic, minimal, probably-virtual deployment, aside from the ones intended for vagrant use. At least not for x86_64. I suppose I'd tend to use virt-install or just install from the network install image, for this kind of use. Maybe we should look at this backwards and try to implement an instance-data injection environment in libvirt, by default. Then it would be possible to use images which contain cloud-init unmodified, and safely. Coming to this thread late. There's been an RFE for virt-manager for a while to send in cloud-init data for cloud images: https://bugzilla.redhat.com/show_bug.cgi?id=981693 That would require using libguestfs to detect that the disk image is a ex. Fedora cloud image. And nowadays I'd lean more towards just disabling cloud-init and setting an empty password instead of doing the specific cloud-init dance. It's not trivial though. The cloud images could give better feedback here, like if no cloud-init data is found in a short period of time then print a message that your cloud is misconfigured our you are using the image incorrectly. I don't know how practical that is though Thanks, Cole ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
I don't know that the cloud images are necessarily not it either though - Randy's vagrant set up uses the vagrant cloud image... Whatever the story is, we should be straight on it! ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Thu, 2018-09-27 at 13:40 +, Máirín Duffy wrote: > So this destroy and re-create philosophy is very counter to my past > development practices :( Does Vagrant have anything built in to set > it up with an Ansible playbook? It does have a hook to call into Ansible. Here's how I do that in my Bodhi Vagrantfile: https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile#L48-L50 signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
* Adam Williamson: > I don't think we ship anything that is exactly a *disk image* for this > kind of non-cloud, non-Atomic, minimal, probably-virtual deployment, > aside from the ones intended for vagrant use. At least not for x86_64. > I suppose I'd tend to use virt-install or just install from the network > install image, for this kind of use. Maybe we should look at this backwards and try to implement an instance-data injection environment in libvirt, by default. Then it would be possible to use images which contain cloud-init unmodified, and safely. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Thu, 2018-09-27 at 13:29 +, Máirín Duffy wrote: > I'm willing to put some skin in the game but it's unclear to me how > we'd lay things out. > > Is anybody interested in meeting up about this and talking through > it? I think the website / positioning / docs type stuff is > addressable, but the big challenge here is figuring out the strategy > we want. > > For example - who is using Server for what? Is the cloud base image > meant for cloud deployments and there's another image targeted for > developers running vms? Are they both under the same edition (right > now cloud base images are shown under atomic) or are they separate > editions? What is that edition / are those editions called? Are they > Fedora Core OS or something else? I don't think we ship anything that is exactly a *disk image* for this kind of non-cloud, non-Atomic, minimal, probably-virtual deployment, aside from the ones intended for vagrant use. At least not for x86_64. I suppose I'd tend to use virt-install or just install from the network install image, for this kind of use. BTW, if you want to see everything we build and try to figure out what it all is, the release validation pages have tables of all the deliverables that got built for the compose under testing, e.g.: https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Installation that's not absolutely everything we *try* to build - images that failed don't show up, of course - but it's a handy starting point. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Thu, Sep 27, 2018 at 01:29:59PM -, Máirín Duffy wrote: > Is anybody interested in meeting up about this and talking through it? I > think the website / positioning / docs type stuff is addressable, but the > big challenge here is figuring out the strategy we want. > > For example - who is using Server for what? Is the cloud base image meant > for cloud deployments and there's another image targeted for developers > running vms? Are they both under the same edition (right now cloud base > images are shown under atomic) or are they separate editions? What is that > edition / are those editions called? Are they Fedora Core OS or something > else? > > On and on. I'm happy to run discussions / brainstorming on the above and > redesign the website (which I've been working on anyway) and help with > marketing / etc. accordingly. Thanks Mo! This would be incredibly valuable. And, yeah, as your questions show, this has drifted from what I still think made sense four years ago (!) when we did this for the F21 release. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Thu, Sep 27, 2018 at 9:41 PM Máirín Duffy wrote: > > > On Wed, 2018-09-26 at 11:04 +, Máirín Duffy wrote: > > Even though I do this, I find it helpful to be able to completely > > destroy the VM and re-create it, knowing that all the information to > > re-create it is in git (via the Vagrantfile + Ansible playbook). Before > > I used it, I would lose time occasionally managing my development VMs, > > or trying to get them working again if something went wrong. Now when > > something goes wrong, I don't even bother trying to figure it out - I > > just destroy and re-create. > > So this destroy and re-create philosophy is very counter to my past > development practices :( Does Vagrant have anything built in to set it up > with an Ansible playbook? Probably this[1] is helpful for you. Regarding the GUI, I think vagrant could be looked like a frontend which sends requests to backend to create or destroy VMs as well as other operations. So, for different backends, its own GUI could be used to manage VMs. It could be virt-manager, VirtualBox, or even the OpenStack website if you use vagrant to create VMs in openstack. [1] https://www.vagrantup.com/docs/provisioning/ansible.html > > ~m > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Regards, Chenxiong Qi ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 14:18 +, Máirín Duffy wrote: > Hi fedora-devel, > > This morning I set out to set up a VM for web development for a project I've > been working on so I could access my development environment from multiple > locations / workstations without having to set it up again and again on > different systems. > > I had a surprisingly difficult time in doing this. The steps I followed, > wanting to interact with the VM via virt-manager [1]: > > - Look at Atomic website page, find link for cloud images, try image > advertised as libvirt (was a box image), try to import into virt-manager, > fail > (not a bootable image) > - Realize that was a dumb move and try again with raw image. Tried to import > into virt-manager, didn't know I have to decompress manually first. Fail. > (not a bootable image) > - Give up on Fedora base cloud image, try server. 3GB download, takes 30 min > to install. Install concludes with somehow either crashing the hypervisor or > disconnecting virt-manager from the hypervisor. > - Realize how heavyweight server seems and it's not going to be good for > something I really wanted to be lean and clean, esp when seeing stuff like > snappy scroll by in the package install list (nothing against snappy, just > not smtg I'd expect in a lean webdev env) > - Get help in an irc development channel, learn I have to extract the raw > image, hurrah, quick results except! Boot stalls. > - Found out it's cloud-info stalling the boot. > - Yay I have a login prompt! What's the login info? Ga... > - Realize have to run virt-customize --uninstall cloud-init --root-password > password:whatever --selinux-relabel -a theimage > - Success finally (ETA 1.5 hrs not 100% fully attended of course) > > Note that: > - I searched the Fedora docs, website, ask Fedora, and did general searches > at each point of failure and didn't find much in the way of guidance. Only in > talking to a couple of knowledegable and helpful folks in real time was I > able to get past the fail points. > - Something else to note that's non obvious is setting up virt manager as > non-root, first answer > https://ask.fedoraproject.org/en/question/45805/how-to-use-virt-manager-as-a-non-root-user/ > > OK so my questions for you, Fedora development community: > > - Is running a lightweight local VM for web development a usecase we want to > support? Is it dare I ask important? > - If so, is what I ended up setting up what we want people in that usecase to > do? (E.g. use Fedora cloud base image, set up in virt-manager or boxes, using > virt-customize to remove cloud-init and configure login password? I suppose my instinct in your case would be just to do a conventional minimal install, either using the Everything netinst image or the Server DVD or netinst image. But I agree that we don't really do a good job of telling people our recommended approach for this kind of use case, or flagging up that the Cloud images are not it, unless you're doing something very specific. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
If you these two steps from documentation: https://developer.fedoraproject.org/tools/vagrant/vagrant-atlas.html the vagrant box appears in virt-manager as another machine. The name of the machine will be derived from the directory name where the Vagrant file is located. Of course it is not smart to do operations such as destroying the Vagrant managed VM from virt-manager. V. Dne 26.9.2018 v 13:06 Máirín Duffy napsal(a): > Is there a way to use a vagrant image that works with virt-manager? > > ~m > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 17:25 -0400, Josh Boyer wrote: > If we think Vagrant is better for this kind of work, we should be > actively looking at producing vagrant images instead. I recommended it because we do produce Vagrant images. From the example Vagrantfile I posted: https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile#L13 We even have docs about it here: https://fedoraproject.org/wiki/Vagrant signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 23:38 +0200, Miro Hrončok wrote: > > We IMHO produce images for vagrant and we document vagrant at the > developer portal: > > https://developer.fedoraproject.org/tools/vagrant/about.html > https://download.fedoraproject.org/pub/fedora/linux/releases/28/Cloud/x86_64/images/ Yeah, we produce multiple Vagrant images, all of these: Cloud_Base Python_Classroom Scientific Atomic(Host) however, it's clear from Mo's experience that this documentation isn't ideally discoverable. Perhaps get.fp.o could be tweaked a bit to help with this sort of use case, with a small-but-prominent box out leading to the developer docs, or something? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
> On Wed, 2018-09-26 at 11:04 +, Máirín Duffy wrote: > Even though I do this, I find it helpful to be able to completely > destroy the VM and re-create it, knowing that all the information to > re-create it is in git (via the Vagrantfile + Ansible playbook). Before > I used it, I would lose time occasionally managing my development VMs, > or trying to get them working again if something went wrong. Now when > something goes wrong, I don't even bother trying to figure it out - I > just destroy and re-create. So this destroy and re-create philosophy is very counter to my past development practices :( Does Vagrant have anything built in to set it up with an Ansible playbook? ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Hi Alex, this is great. Thanks for pointing me at it! Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
I'm willing to put some skin in the game but it's unclear to me how we'd lay things out. Is anybody interested in meeting up about this and talking through it? I think the website / positioning / docs type stuff is addressable, but the big challenge here is figuring out the strategy we want. For example - who is using Server for what? Is the cloud base image meant for cloud deployments and there's another image targeted for developers running vms? Are they both under the same edition (right now cloud base images are shown under atomic) or are they separate editions? What is that edition / are those editions called? Are they Fedora Core OS or something else? On and on. I'm happy to run discussions / brainstorming on the above and redesign the website (which I've been working on anyway) and help with marketing / etc. accordingly. Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:46 -0400, Randy Barlow wrote: > I ssh to the big system and do all my Vagrant work there. Heh, sorry for so many posts, but I wanted to add to this that it is also possible to point your Vagrantfile at a remote libvirt server. This lets you run Vagrant on your laptop, but have the VM run on some other server. That can be kinda nifty too if you don't want to ssh to the other system for some reason (like if you use an IDE). I personally just work in terminals all day with vim, so I don't do that, but it's possible and might be interesting to you ☺ signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 17:25 -0400, Josh Boyer wrote: > The conversation > went like this: > > Hey, I'm trying to do this and all the documented Fedora > things are really hard or poorly documented. Is this how Fedora > should work? > Oh, use this thing that *Fedora doesn't produce* in a > manner that *Fedora doesn't document* instead. It's much better! > > That is a really bad anti-pattern. > > If we think Vagrant is better for this kind of work, we should be > actively looking at producing vagrant images instead. Fedora does produce Vagrant images. From the example Vagrantfile I posted in my first reply, you can see that I'm pulling the Vagrantfile from Fedora (anyone who does this should really add that checksum line too): https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile#L13 In addition to the docs that Miro linked, we have also documented it here: https://fedoraproject.org/wiki/Vagrant signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:04 +, Máirín Duffy wrote: > - There is no GUI for it that I can find. I just like GUIs, > especially for this sort of work that I might do for a stretch at a > time and then not have to do for months afterwards and have to > relearn next time. I don't know of a GUI for Vagrant itself, so yeah that's a deficiency. As I noted in my other e-mail, you can use virt-manager for the non- create/destroy actions, but to my knowledge you can't escape writing a little Ruby and using a little bit of CLI. > - I have had - I have been told coincidentally and with just terrible > luck - horrible experiences with vagrant. You aren't alone. I too have had unfun experiences, especially if it gets confused about its state. State is kept in no fewer than three places - in your project dir there's a .vagrant, there's a ~/.vagrant.d, and it keeps some state in libvirt too. If these get out of sync (which can happen if a VM gets destroyed without Vagrant's knowledge) it's super hard to get it working again. I've found that going and just deleting those three places and restarting libvirt can get it back to a clean state, but yeah it's painful. > - My use case here is I have a big beefy workstation, and a few > different laptops. I don't want to have to set the environment up > multiple times or be moving large files around. I just want to set up > the environment once, and be able to ssh into it from wherever. I'm > not too worried about damage bc I can clone the VM once I have > everything working and setup, and everything else should be in git > anyway. FWIW, this is also my use case, but I still use Vagrant. I use a laptop as my workstation, and have the big beefy workstation as a headless server. I ssh to the big system and do all my Vagrant work there. This way my laptop's battery life is way better when I'm on the move, and that big system is faster anyway. Even though I do this, I find it helpful to be able to completely destroy the VM and re-create it, knowing that all the information to re-create it is in git (via the Vagrantfile + Ansible playbook). Before I used it, I would lose time occasionally managing my development VMs, or trying to get them working again if something went wrong. Now when something goes wrong, I don't even bother trying to figure it out - I just destroy and re-create. This is also nice if you want to try out things that might be destructive. Whatever solution you go for, I do recommend you find one that gives you this quality because it will save you time. Using containers would also achieve this goal if that interests you. You can use Vagrant to run your containers too ☺ > Does that make sense or am I trying to fit a square peg in a round > hole here? Yeah makes sense. Vagrant is certainly not perfect and isn't going to fit everyone's needs. I find it overall saves me time and I've spent enough time with it to learn to work around its weird problems so they don't bother me as much anymore. signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:06 +, Máirín Duffy wrote: > Is there a way to use a vagrant image that works with virt-manager? I'll say "sort of" here. If you use vagrant-libvirt, you would use the vagrant CLI to launch/provision the VM, but once it's running you can see it in virt-manager and interact with its console there. You would still want to use the vagrant CLI to destroy it when done otherwise Vagrant will freak out (it freaks out when the state of things is not as expected, which is one of its warts.) So tl;dr; you use vagrant to create/destroy, but can use virt-manager in between if you like. signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, Sep 25, 2018 at 02:18:50PM -, Máirín Duffy wrote: > - Is running a lightweight local VM for web development a usecase we want to > support? Is it dare I ask important? Yeah. I think we really need to straighten out the Fedora Cloud / Fedora Server image thing. As I understand it, everyone is basically agreed but it's hard to find time to *do*. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Hi Máirín, For several years now I've been using VMs with backing files to do what you're trying to achieve. It's basically what Dusty Mabe describes in the last paragraph of this article: https://dustymabe.com/2015/01/11/qemu-img-backing-files-a-poor-mans-snapshotrollback/ Using virt-manager, I set up my base VM exactly the way I want it. Next, I use qemu-img to create as many additional VMs as I need for each project. The disk space they consume is just their delta from the base image. The new files can then be imported into virt-manager and used as regular images, as long as the base image remains unchanged. Use of the terminal is only required when making the snapshots: qemu-img create -f qcow2 -o backing_file=base_env.img test01.img It's not as involved or elegant as using vagrant and ansible, but it's simple and if you are already familiar with virt-manager, you do not need to get acquainted with anything else. Best regards, Alex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Dne 26.9.2018 v 13:28 Vít Ondruch napsal(a): > If you these two steps from documentation: > > https://developer.fedoraproject.org/tools/vagrant/vagrant-atlas.html > > the vagrant box appears in virt-manager as another machine. The name of > the machine will be derived from the directory name where the Vagrant > file is located. > > Of course it is not smart to do operations such as destroying the > Vagrant managed VM from virt-manager. OTOH some other operations, such as removing unused vagrant images are doable only by tools such as virt-manager :/ V. > > > V. > > > Dne 26.9.2018 v 13:06 Máirín Duffy napsal(a): >> Is there a way to use a vagrant image that works with virt-manager? >> >> ~m >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
I just tried it. I was able to connect to remote hypervisor, it showed my VM - pretty impressive. It was a little flaky in that when I right clicked to view properties of the VM it hung (with a, wait / force quit dialog popping up) but I was eventually able to load the dialog. It seems to allow memory configuration and snapshotting, but not storage. The latter is an issue bc the Fedora default image is 4 GB and that wasn't enough for my env, I'm currently trying to deal with how to resize the file system (was able to make image being using libvirt commands.) FWIW! Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
So the environment I'm trying to set up involves a backend that consists of three separate containers, and the web front end is separate from that. Because setting up the environment is a difficult task, I'd like it in a VM so I can clone it once it's configured so that I can reproduce it without having to do everything from scratch. And I will just put this out there - the upstream I'm working with, the scripts / instructions are written for OS X, Ubuntu, and docker. I've already dealt with a few snags once I got the base Fedora VM set up - issues with networking (no ifconfig on the base image which is like typing on a keyboard wearing mittens for me), Docker by default installed via Fedora RPM *not* configured with the --selinux-enabled flag in the systemd service file, SELinux avc denials even with that enabled, and now some other issues I'm going to spend hours today figuring out I'm assuming. Once I get it working as scripted by upstream, I would like to get it working with cri-o & friends instead of docker. This is not the kind of work I'd want to do on my baremetal machine because its my primary workstation and I don't want to screw. I hope it makes sense, my logic here. Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Is there a way to use a vagrant image that works with virt-manager? ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Hi Randy, I did consider Vagrant but there are a few issues with it: - There is no GUI for it that I can find. I just like GUIs, especially for this sort of work that I might do for a stretch at a time and then not have to do for months afterwards and have to relearn next time. - I have had - I have been told coincidentally and with just terrible luck - horrible experiences with vagrant. The very first time I tried to use it, there was some kind of bug with the kernel support for it - I don't remember the details - but it amounted to a race condition that with my particular hardware somehow always resulted in a crashing and unworkable environment that ended up eating 2 full workdays to debug. It pretty much sucked. The other experience I've had with it is at a couple of hackfests at conferences, where it involved downloading large files the wifi couldn't handle and passing around USB keys, taking 30 min or more to get the base environment running, and it eating up disk space and generally making my system run slow for weeks afterwards (I think someone trying to help me get it working at one point set it to start on boot which I didn't realize until weeks later after frequently losing my desktop stability to OOM killing.) - My use case here is I have a big beefy workstation, and a few different laptops. I don't want to have to set the environment up multiple times or be moving large files around. I just want to set up the environment once, and be able to ssh into it from wherever. I'm not too worried about damage bc I can clone the VM once I have everything working and setup, and everything else should be in git anyway. Does that make sense or am I trying to fit a square peg in a round hole here? Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, Sep 25, 2018 at 8:18 AM, Máirín Duffy wrote: > - Is running a lightweight local VM for web development a usecase we want to > support? Is it dare I ask important? In ancient times I just ran a local httpd instance. VM seems heavy weight for this, but yes it should totally work, albeit using more memory. I'm guessing 500MiB? In the last couple months I started running into weird Android battery life problems, and discovered Battery Historian. And quickly discovered the github project offers a Docker container. I'm a Docker lightweight. But I ran the recipe for installing and running it, which I vaguely recall amounted to one or two lines, pointed my browser to the IP + port for the container, and it worked. It takes a few seconds to "boot" and uses maybe 5MiB memory, and perhaps upwards of 80MiB while it's processing an Android bug report - then spits out pretty graphs. I've run it locally and on a remove NUC, same command, just change the IP address I point my web browser to. I know, containers! Shiny new thing! But it really was easier to deal with for this use case than setting up a VM. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 23:38 +0200, Miro Hrončok wrote: > https://developer.fedoraproject.org/tools/vagrant/about.html Oh nice, I hadn't seen these docs before. Thanks for sharing! signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On 25.9.2018 23:25, Josh Boyer wrote: On Tue, Sep 25, 2018 at 4:46 PM Randy Barlow wrote: On Tue, 2018-09-25 at 14:18 +, Máirín Duffy wrote: - Is running a lightweight local VM for web development a usecase we want to support? Is it dare I ask important? - If so, is what I ended up setting up what we want people in that usecase to do? (E.g. use Fedora cloud base image, set up in virt- manager or boxes, using virt-customize to remove cloud-init and configure login password? Hi Máirín! Have you considered using Vagrant for this? It makes it easy to script a reproducible development virtual machine, so that you can quickly destroy and recreate it on demand. I use it to develop Bodhi and I've been mostly pretty happy with it (it does have some weird warts too, but mostly works well). Bodhi uses Vagrant to start up the guest, and then Vagrant asks Ansible to configure it to be a Bodhi dev box. Here's the file that makes it go: https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile The playbook Vagrant runs is here: https://github.com/fedora-infra/bodhi/tree/3.10.0/devel/ansible And here are instructions that describe what it's like for a developer to use it: https://github.com/fedora-infra/bodhi/blob/3.10.0/docs/developer/vagrant.rst I recommend this or something like this over making a more "permanent" VM, because it makes it easy to share the valuable development environment with others (or even with yourself on multiple machines), and because it makes it a non-issue when the guest gets damaged in some way (rather than spending time debugging a guest I've broken, I just vagrant destroy && vagrant up, go make some coffee, and when I'm back I have a fresh working instance again). OK. So this suggestion is well intentioned. It's even a good one, IMHO. However, look at this from a non-Fedora view. The conversation went like this: Hey, I'm trying to do this and all the documented Fedora things are really hard or poorly documented. Is this how Fedora should work? Oh, use this thing that *Fedora doesn't produce* in a manner that *Fedora doesn't document* instead. It's much better! We IMHO produce images for vagrant and we document vagrant at the developer portal: https://developer.fedoraproject.org/tools/vagrant/about.html https://download.fedoraproject.org/pub/fedora/linux/releases/28/Cloud/x86_64/images/ -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, Sep 25, 2018 at 4:46 PM Randy Barlow wrote: > > On Tue, 2018-09-25 at 14:18 +, Máirín Duffy wrote: > > - Is running a lightweight local VM for web development a usecase we > > want to support? Is it dare I ask important? > > - If so, is what I ended up setting up what we want people in that > > usecase to do? (E.g. use Fedora cloud base image, set up in virt- > > manager or boxes, using virt-customize to remove cloud-init and > > configure login password? > > Hi Máirín! > > Have you considered using Vagrant for this? It makes it easy to script > a reproducible development virtual machine, so that you can quickly > destroy and recreate it on demand. I use it to develop Bodhi and I've > been mostly pretty happy with it (it does have some weird warts too, > but mostly works well). Bodhi uses Vagrant to start up the guest, and > then Vagrant asks Ansible to configure it to be a Bodhi dev box. Here's > the file that makes it go: > > https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile > > The playbook Vagrant runs is here: > > https://github.com/fedora-infra/bodhi/tree/3.10.0/devel/ansible > > And here are instructions that describe what it's like for a developer > to use it: > > > https://github.com/fedora-infra/bodhi/blob/3.10.0/docs/developer/vagrant.rst > > I recommend this or something like this over making a more "permanent" > VM, because it makes it easy to share the valuable development > environment with others (or even with yourself on multiple machines), > and because it makes it a non-issue when the guest gets damaged in some > way (rather than spending time debugging a guest I've broken, I just > vagrant destroy && vagrant up, go make some coffee, and when I'm back I > have a fresh working instance again). OK. So this suggestion is well intentioned. It's even a good one, IMHO. However, look at this from a non-Fedora view. The conversation went like this: Hey, I'm trying to do this and all the documented Fedora things are really hard or poorly documented. Is this how Fedora should work? Oh, use this thing that *Fedora doesn't produce* in a manner that *Fedora doesn't document* instead. It's much better! That is a really bad anti-pattern. If we think Vagrant is better for this kind of work, we should be actively looking at producing vagrant images instead. Then people would have the documentation and tools they need. If we don't think Vagrant is a good solution here, we should be working to improve the solutions we have and documentation for them to make them less confusing. If we do neither of those things, is going to be left wondering why they used Fedora in the first place. josh ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 16:45 -0400, Randy Barlow wrote: > And here are instructions that describe what it's like for a > developer > to use it: > https://github.com/fedora-infra/bodhi/blob/3.10.0/docs/developer/vagrant.rst Here is a rendered version of that pag https://bodhi.fedoraproject.org/docs/developer/vagrant.html signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 14:18 +, Máirín Duffy wrote: > - Is running a lightweight local VM for web development a usecase we > want to support? Is it dare I ask important? > - If so, is what I ended up setting up what we want people in that > usecase to do? (E.g. use Fedora cloud base image, set up in virt- > manager or boxes, using virt-customize to remove cloud-init and > configure login password? Hi Máirín! Have you considered using Vagrant for this? It makes it easy to script a reproducible development virtual machine, so that you can quickly destroy and recreate it on demand. I use it to develop Bodhi and I've been mostly pretty happy with it (it does have some weird warts too, but mostly works well). Bodhi uses Vagrant to start up the guest, and then Vagrant asks Ansible to configure it to be a Bodhi dev box. Here's the file that makes it go: https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile The playbook Vagrant runs is here: https://github.com/fedora-infra/bodhi/tree/3.10.0/devel/ansible And here are instructions that describe what it's like for a developer to use it: https://github.com/fedora-infra/bodhi/blob/3.10.0/docs/developer/vagrant.rst I recommend this or something like this over making a more "permanent" VM, because it makes it easy to share the valuable development environment with others (or even with yourself on multiple machines), and because it makes it a non-issue when the guest gets damaged in some way (rather than spending time debugging a guest I've broken, I just vagrant destroy && vagrant up, go make some coffee, and when I'm back I have a fresh working instance again). signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Il giorno mar 25 set 2018 alle 16:18, =?iso-8859-1?b?TeFpcu1u?= Duffy ha scritto: [1] Note I used virt-manager bc other webdevs I know use it and I'm familiar with using it for connecting to remote hypervisors which was a main thing I wanted to do. Happy to use Boxes if it allows that since it looks so slick, don't know enough about it to know if it does! Yes, it does: https://help.gnome.org/users/gnome-boxes/stable/connect.html but I've never tried it with remote machines ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, Sep 25, 2018 at 10:54 AM Peter Robinson wrote: > > > * Máirín Duffy: > > > > > - Found out it's cloud-info stalling the boot. > > > > I think it's actually cloud-init. > > > > > - Yay I have a login prompt! What's the login info? Ga... > > > - Realize have to run virt-customize --uninstall cloud-init > > > --root-password password:whatever --selinux-relabel -a theimage > > > > I have requested downstream that we ship separate KVM and cloud images > > because cloud-init is a significant security risk when run outside a > > cloud environment which supports instance data injection (which libvirt > > does not provide). cloud-init probes the network and executes scripts > > it finds there as root. It cannot perform authentication because it > > performs customization of the image, and the owner of the VM is not > > known to it before it runs. > > > > A dedicated cloud image with a document procedure for injecting > > authentication information (could be an open root shell on the serial > > console) would help your use case as well and discourage people from > > abusing the insecure cloud images for KVM installs. > > Might be better to move them all to ignition in F-30? How is ignition any better? Aside from it being written in Go (which reduces the architectures and platforms that can be supported), it functions more or less the same way as cloud-init. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
> * Máirín Duffy: > > > - Found out it's cloud-info stalling the boot. > > I think it's actually cloud-init. > > > - Yay I have a login prompt! What's the login info? Ga... > > - Realize have to run virt-customize --uninstall cloud-init --root-password > > password:whatever --selinux-relabel -a theimage > > I have requested downstream that we ship separate KVM and cloud images > because cloud-init is a significant security risk when run outside a > cloud environment which supports instance data injection (which libvirt > does not provide). cloud-init probes the network and executes scripts > it finds there as root. It cannot perform authentication because it > performs customization of the image, and the owner of the VM is not > known to it before it runs. > > A dedicated cloud image with a document procedure for injecting > authentication information (could be an open root shell on the serial > console) would help your use case as well and discourage people from > abusing the insecure cloud images for KVM installs. Might be better to move them all to ignition in F-30? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
* Máirín Duffy: > - Found out it's cloud-info stalling the boot. I think it's actually cloud-init. > - Yay I have a login prompt! What's the login info? Ga... > - Realize have to run virt-customize --uninstall cloud-init --root-password > password:whatever --selinux-relabel -a theimage I have requested downstream that we ship separate KVM and cloud images because cloud-init is a significant security risk when run outside a cloud environment which supports instance data injection (which libvirt does not provide). cloud-init probes the network and executes scripts it finds there as root. It cannot perform authentication because it performs customization of the image, and the owner of the VM is not known to it before it runs. A dedicated cloud image with a document procedure for injecting authentication information (could be an open root shell on the serial console) would help your use case as well and discourage people from abusing the insecure cloud images for KVM installs. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora for Web Development fail
Hi fedora-devel, This morning I set out to set up a VM for web development for a project I've been working on so I could access my development environment from multiple locations / workstations without having to set it up again and again on different systems. I had a surprisingly difficult time in doing this. The steps I followed, wanting to interact with the VM via virt-manager [1]: - Look at Atomic website page, find link for cloud images, try image advertised as libvirt (was a box image), try to import into virt-manager, fail (not a bootable image) - Realize that was a dumb move and try again with raw image. Tried to import into virt-manager, didn't know I have to decompress manually first. Fail. (not a bootable image) - Give up on Fedora base cloud image, try server. 3GB download, takes 30 min to install. Install concludes with somehow either crashing the hypervisor or disconnecting virt-manager from the hypervisor. - Realize how heavyweight server seems and it's not going to be good for something I really wanted to be lean and clean, esp when seeing stuff like snappy scroll by in the package install list (nothing against snappy, just not smtg I'd expect in a lean webdev env) - Get help in an irc development channel, learn I have to extract the raw image, hurrah, quick results except! Boot stalls. - Found out it's cloud-info stalling the boot. - Yay I have a login prompt! What's the login info? Ga... - Realize have to run virt-customize --uninstall cloud-init --root-password password:whatever --selinux-relabel -a theimage - Success finally (ETA 1.5 hrs not 100% fully attended of course) Note that: - I searched the Fedora docs, website, ask Fedora, and did general searches at each point of failure and didn't find much in the way of guidance. Only in talking to a couple of knowledegable and helpful folks in real time was I able to get past the fail points. - Something else to note that's non obvious is setting up virt manager as non-root, first answer https://ask.fedoraproject.org/en/question/45805/how-to-use-virt-manager-as-a-non-root-user/ OK so my questions for you, Fedora development community: - Is running a lightweight local VM for web development a usecase we want to support? Is it dare I ask important? - If so, is what I ended up setting up what we want people in that usecase to do? (E.g. use Fedora cloud base image, set up in virt-manager or boxes, using virt-customize to remove cloud-init and configure login password? If yes to both, I would be happy to help improving docs / websites / etc. to support the use case as well as filing some RFEs in the tools to make the experience better (e.g., if virt-manager could recognize a compressed raw image and offer to decompress it or at least tell user to do so, would be a win, for example.) But if I'm doing something edge-casey or not meant to be done, obviously that's a wasted effort. Let me know what you think! Cheers, ~m [1] Note I used virt-manager bc other webdevs I know use it and I'm familiar with using it for connecting to remote hypervisors which was a main thing I wanted to do. Happy to use Boxes if it allows that since it looks so slick, don't know enough about it to know if it does! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
