Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish provider 'libvirt' #55

Open
ottok opened this issue Nov 5, 2018 · 2 comments
Open

Publish provider 'libvirt' #55

ottok opened this issue Nov 5, 2018 · 2 comments

Comments

@ottok
Copy link
Contributor

ottok commented Nov 5, 2018

Steps for current demo:

# Assuming original box name is seravo/wordpress-beta version 0
qemu-img convert -f vmdk -O qcow2 ~/.vagrant.d/boxes/seravo-VAGRANTSLASH-wordpress-beta/0/virtualbox/*.vmdk seravo-wordpress-beta.img
/usr/share/doc/vagrant-libvirt/examples/create_box.sh seravo-wordpress-beta.img
vagrant box add seravo-wordpress-beta.box --name seravo/wordpress-beta

cd ~/wordpress-project
wordpress-project$ vagrant up --provider libvirt

Currently fails with missing vagrant-wordpress0 network. Needs more research to complete..

@ottok
Copy link
Contributor Author

ottok commented Nov 5, 2018

Now a libvirt version of current wordpress-beta is available in case somebody wants to play around with it and try to get the Vagrantfile part correctly configured.

image

@ottok
Copy link
Contributor Author

ottok commented Jan 27, 2021

Note that the Travis-CI file generates a libvirt box on every commit, as it uses it to run and test the box (one cannot run VirtualBox on Travis-CI). Testing and publishing the image to the public to use would be fairly easy, but this would server only Linux users, and they might prefer Docker instead, so maybe not worthwhile to complete.

@ottok ottok added the wontfix label Jan 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant