On 07/10/2015 10:27 AM, Michael Vermaes wrote:
On Fri, Jul 10, 2015 at 5:36 AM, Karanbir Singh <mail-lists@karan.org mailto:mail-lists@karan.org> wrote:
On 09/07/15 12:23, Michael Vermaes wrote: > Hello, in addition to the other comments, I just wanted to say that it > would be great to have an 'official' vmware_desktop Vagrant box > available on Atlas as well. > > Let me know if there's anything I can do to help enable that. I found > this bugzilla issue which could maybe be used for tracking the various > requirements? > > https://bugs.centos.org/view.php?id=6365 > > Thanks, > > Michael I believe the vbox image should work as-is with the vmware provider as well ? is that something you might be able to try ? - KB Thanks for the suggestion. Here's the message I received when I tried to 'vagrant up' after ' vagrant init centos/7 '
Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: Box 'centos/7' could not be found. Attempting to find and install... default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation default: Box Version: >= 0 ==> default: Loading metadata for box 'centos/7' default: URL: https://atlas.hashicorp.com/centos/7 The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it.
If you're adding a box from HashiCorp's Atlas, make sure the box is released.
Name: centos/7 Address: https://atlas.hashicorp.com/centos/7 Requested provider: ["vmware_desktop", "vmware_fusion", "vmware_workstation"]
Based on your comment, it sounds like the underlying image should be compatible with VMware, it probably just needs to be uploaded again specifying that it is also valid for the vmware_desktop provider.
This error is expected if you are using atlas.hashicorp.com/centos/7 https://atlas.hashicorp.com/centos/7 as we don't have vmware provider released there.
Can you please try the below [1] image. You have have to manually download the image then add it to Vagrant. Lets me know if you need any help on that.
[1] http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505...
Similarly to Jeff's request about Guest Additions for VirtualBox, it would be ideal to have the VMware Tools preinstalled in this box - this is a requirement for shared folders to work. If the CentOS 7 image is built from https://github.com/CentOS/sig-cloud-instance-build/blob/master/vagrant/cento..., I think it would be a matter of including open-vm-tools in the list of packages, to get access to /usr/lib64/libhgfs.so.
Yeah thats the ks file used for creating the Vagrant box.
> > On Thu, Jul 9, 2015 at 3:18 PM, Timothy Rees <reestr.uk@gmail.com <mailto:reestr.uk@gmail.com> > <mailto:reestr.uk@gmail.com <mailto:reestr.uk@gmail.com>>> wrote: > > I would suggest keeping the root volume as minimal as possible for the > box and then let the end users to grow it using methods provided by > Vagrant. Anyone then can grow the volume to their specific use case, > its a lot easier than reducing a default, large disk provided with a > box. > > Cheers, > Tim > > On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com <mailto:lmohanty@redhat.com> > <mailto:lmohanty@redhat.com <mailto:lmohanty@redhat.com>>> wrote: > > On 07/08/2015 10:32 PM, Jeff Sheltren wrote: > >> > >> Hi, I've started doing some testing on the Virtualbox Vagrant box > >> > (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505-x86_64-01.box) > >> > >> I've hit a couple of issues: > >> > >> 1) The disk size, at about 8 GB, is too small. Could it be bumped to > >> 50-100 GB? Since the on-disk image will grow dynamically this > won't take up > >> that much space by default but will make it usable for those that > need more > >> storage on the root partition (and I don't want to have to custom > mount > >> additional partitions). > >> > > > > Yes, this can be fixed. I am fine with bumping the disk size to > 50GB as it > > would be sparse disk. Also there are few tricks you can do with the > > Vagrantfile to increase the disk size. But I have not tried them > > > >> 2) The VirtualBox Guest Additions aren't included. I'm assuming > this is > >> due to a licensing issue and not that they were simply not > considered but > >> wanted to double check. > >> > > > > This part I am not sure. I need to check how we can add > "VirtualBox Guest > > Additions". yes, we want to fix this. > >> > >> Otherwise it's been great, and saves me having to build my own > custom box, > >> which is definitely a win. > >> > >> -Jeff > > > > > > How do we track these issues? I just dont want to loose track of > these. > > > > -Lala > > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh <http://twitter.com/kbsingh> GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel