garethr / vagrantboxes-heroku Goto Github PK

Fedora 18 x86 Minimal (with Chef 11.4.0, VirtualBox Guest Additions 4.2.10 and rpmfusion enabled)

This VM is just not working correctly. I can not reach any service, except ssh. Iptables not running, SELinux disabled - no idea whats wrong with this box.

It would help to verity if the downloaded file is correct.

Looks like http://puppetlabs.s3.amazonaws.com/pub/squeeze64.box is not valid anymore.

please check the thread - hashicorp/vagrant#653, I received similar error message wile trying to setup this box.

thanks

https://www.dropbox.com/s/0wi7banhr0bryg0/debian-7.7-puppet.box?dl=1

There appears to be problems with this box:

CentOS 6.4 x86_64 Minimal VMware Fusion (VMware Tools, Chef 11.4.0, Puppet 3.1.1) https://dl.dropbox.com/u/5721940/vagrant-boxes/vagrant-centos-6.4-x86_64-vmware_fusion.box

I am unable to get certain system level apps to recognize the share, ie. httpd chokes on /vagrant as DocumentRoot. I believe this image should probably be removed as it does not appear to be functional.

It seems Ubuntu box added at issue #71 has no Puppet installed:

$ ...
$ [default] Running provisioner: Vagrant::Provisioners::Pupet...

The puppet binary appears to not be in the PATH of the guest. This
could be because the PATH is not properly setup or perhaps Puppet is not
installed on this guest. Puppet provisioning can not continue without
Puppet properly installed.

That way people don't waste time downloading boxes for a provider that they don't have.

Both of these links are broken:
https://s3.amazonaws.com/vagrant_boxen/freebsd_amd64_ufs.box
https://s3.amazonaws.com/vagrant_boxen/freebsd_amd64_zfs.box

The box "Debian Wheezy amd64 (Puppet, VirtualBox)" at https://dl.dropboxusercontent.com/u/86066173/debian-wheezy.box gives error:

Failed to untar the box file. This is usually because you're
attempting to add a box that isn't a valid box file. Please
double check that the box file is properly packaged.

Tried several times to add the box in question, keep getting the same error.

It seems like this arch linux box has a broken ovf file. I get this error message when I try to bring the box to life using vagrant.

I'm not sure how best to report this. Please direct me to post this in a more appropriate location if necessary.

Width of table more then than windows. Showing horizontal scrolling.

I just figured out share links are like symbolic links.

Dropbox share link is similar to symbolic link (a pointer to file name) , it is a pointer to /folder_name/file_name under Dropbox root folder, for example:
https://dl.dropbox.com/s/zmitpteca72sjpx/oracle64.box -> ~/Dropbox/DevOps/vagrantbox.es/oracle64.box

The share links are generated based on the path + file name with a unique token. This makes updating (rm/mv, cp/rsync, mv done!) files, especially vagrant base boxes without changing the share link possible, as long as file name stays the same (under the same folder).

This can probably help to reduce pull requests because it makes updating base boxes without changing the share link (no need to fork and send PR) possible;-)

I think it's a good idea to cascade this tip to vagrantbox.es contributors who are using Dropbox to host base boxes.

http://www.vagrantbox.es/ reads "last updated on May 20th, 2014", but includes e7e750e (search for "2014-06-20" on vagrantbox.es).

Probably the date needs an update.

Clicking "Size (MB)" to sort by size doesn't work correctly because it sorts by text rather by number. This probably used to work because datatables tries to detect automatically if a column has numbers: http://datatables.net/development/type-detection
But some of the images have sizes like "1.8GB", so datatables most likely thinks the column is text. Fixing those to MB sizes, i.e. just numbers, should fix the sorting again.

On a side note, why do you embed the whole datatables js script in the page? It's not even minimized and needlessly blows up the size of the page.

Just went to download from http://timhuegdon.com/vagrant-boxes/Ubuntu-11.10.box and I am receiving a 404 error.

→ vagrant box add ubuntu-11 http://timhuegdon.com/vagrant-boxes/Ubuntu-11.10.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://timhuegdon.com/vagrant-boxes/Ubuntu-11.10.box
Bad status code: 404

Please verify that the box exists and is accessible. Also verify that
this computer is properly connected to the internet.

Might be worth checking the host status and whether this is still provided.

Can you add the AsteriskNow disto in the boxes?
thank of lot

http://images.ansolabs.com/vagrant/oneiric64.box will not work anymore. This url will now resolve to sitescout who has the ip address now that the site has been shutdown and ip released.

Dead links for Debian 7.4.0 Vanilla and Debian 7.4.0 Chef

https://dl.dropboxusercontent.com/s/3jz559mjz2aw4gs/debian-wheezy-64-vanilla.box
https://dl.dropboxusercontent.com/s/cd583cuf0mbcix7/debian-wheezy-64-chef.box

In the same way that people currently list like this:

<tr>
<td>Box Contents</td>
<td>Provider</td>
<td>URL</td>
<td>Size</td>
</tr>

Perhaps we could list them like this

<tr>
<td>Box name</td>
<td>VAGRANT CLOUD - Provider</td>
<td>vagrant init user/box</td>
<td />
</tr>

The vagrant init user/box line matches the text on the vagrantcloud.com site.

This link is dead: https://dl.dropboxusercontent.com/u/86066173/debian-wheezy.box

Could I use another link for this?

Now that vagrant cloud has been released, will this repository be deprecated anytime soon? Or will this still be available for Vagrant pre-1.5.0 users?

A very minor annoyance: after clicking the "Copy" button (implemented as a flash object), the focus stays inside the flash application, which means most keyboard shortcuts do not work (e.g. ctrl+tab to switch to the next tab). Would it be possible to return the focus to the web page after copying to the clipboard?

It'd be great to put that list via an API so it can be hit via curl!

The arch linux box listed here (http://vagrant.pouss.in/archlinux_2012-07-02.box) does not include Puppet and so will not function with the Puppet provisioner. It would be nice if this list was either (a) a list of boxes known to fully support vagrant, or (b) differentiated between those that do and those that don't.

The following entry is incorrect... It says "Ubuntu 13.10" but it is actually "Ubuntu 13.04"...

Official Ubuntu 13.10 daily Cloud Image amd64 (Development release, No Guest Additions) VirtualBox Copy http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box

The following message keeps showing at startup

New release '13.10' available.
Run 'do-release-upgrade' to upgrade to it.

Since GitHub announced that they won't support uploads and that downloads are deprecated , will the github download URL's work ? Here's the link to the post by Github

Hi,

Is there a reason there aren't any windows boxes? I'm assuming it's a liscensing issue...

If not, I'm happy to throw a Win 2008 box on dropbox and host it 👍

hi
i've tried to use one of your boxes, more precisely CentOS 6.4 x86_64 Minimal (VirtualBox Guest Additions 4.2.12, Chef 11.4.4, Puppet 3.1.1)
i've set port forwarding for vagrant (80 -> 8080) but iptables running on the machine blocked my connection.
i suggest rebuilding the box without any firewall running by default.

Great list of boxes, thanks @garethr

Wouldn't it be handy if the list also said which version of chef-client is installed on them?

Nevermind, same as issue #74

If torrents were available, it would reduce the load on the respective hosts. Just a thought.

Hi
Since the list is popular and links starts to get old,
the info might be easier to update with Text data file / CSV / JSON.

It would be easier to maintain:
records can be marked (new, active, offline, old),
category / family can be added easily,
and a link validator can run easily on the data file from browser or some backend periodic job.

Thanks
ZD

Right now when downloading several of the Vagrant boxes from http://www.vagrantbox.es/, I found out only after running them that Chef in them are outdated and doesn't support the software stack I need to run.

So, it would be nice to have additional columns on the page which tell when a particular box was added and what version of Chef does it include. This will help us avoid unnecessary downloads of large files.

Each contributor should fill out these columns when contributing their Vagrant boxes.

Vagrant is complaining about that, not sure if anyone else is having the same problem.

[default] No guest additions were detected on the base box for this VM! Guest
additions are required for forwarded ports, shared folders, host only
networking, and more. If SSH fails on this machine, please install
the guest additions and repackage the box to continue.

This is not an error message; everything may continue to work properly,
in which case you may ignore this message.

Enhancement request for a 64bit Windows box.

The current "Windows 8 with IE 11" is 32bit which should really be mentioned on the download link table.

64bit is a real requirement for a lot of software now on Windows 8 so the current box is kinda useless for software development and testing :(

The Ubuntu raring 64 vanilla box with link: http://goo.gl/ceHWg is missing (dead link) and doesn't work any more. This should be updated or removed.

Hey @garethr,

As I told you on twitter, I did a 2 hours spike on porting the website to Jekyll so that we can use GitHub pages. The code is available at https://github.com/fgrehm/vagrantboxes-gh-pages, is live at http://fgrehm.github.io/vagrantboxes-gh-pages/ and I'm creating this issue so that we can discuss the move :-)

Here's a list of some pain points we experience with the current approach that I believe can be solved with the move:

• Boxes are automatically ordered by name
• Reduce the chances of a PR conflict by having base boxes "metadata" on separate files
• Stop relying on Travis / Heroku (GitHub takes care of deployment and hosting for us ;)
• Although I haven't tried, I'm pretty sure this will open up for us to write a Ruby script that interacts with the Jekyll API to gather base boxes metadata and identifies broken links.

So, if we decide to switch over to that approach, here's a few things we'll need to think about:

• Is there any extra metadata we want around? There's an intention of keeping track of the users who submitted the box to display on the website. If there's something else we want to keep track of this is the time to introduce them.
• Can we make the "last updated at" date dynamic? I always forget to update it and if we are able to somehow fetch that from git commits or from the base boxes "posts" it would be just great.
• What should we do about the current PRs that are open? IMHO we should just close the PR and ask the contributor to submit a new one using the new format as I don't believe it is worth the trouble to deal with a whole bunch of conflicts that will show up.

There are also a couple things that I can't take care from my side. Namely switching the project's default branch to gh-pages and updating DNS entries.

I think that's it, I hope you like it and I'll let you know if I end up remembering something else :-)

Arch Linux 64 (2012-07-02) seems to have kicked the bucket

Currently it is - in theory - possible that somebody installs bad stuff in a box and add the infected box to this list (keyloggers that grab your git key/pw for example, please correct me if i'm wrong here). There should be something to verify the "cleanness" of a box, like user ratings etc.

I set up the box "debian-607-x64" and while the user "vagrant" has the standard password ("vagrant"), the root user uses another password. How can I retrieve the correct password or is there any way to reset the password for root?

I was looking to sort the long list of boxes, perhaps implementing dates can help others as well?

CentOS 6.3 x86_64 minimal
https://dl.dropbox.com/u/7225008/Vagrant/CentOS-6.3-x86_64-minimal.box

The heroku build does not boot when using the latest vagrant. vagrant-heroku fixed this with
ejholmes/vagrant-heroku@08227bc

It might be nice to let users know what size download they're in store for.

Now that Vagrant supports the config.vm.box_download_checksum settings, it would be convenient to have the checksums provided for each box.

root@envprov1:/mnt/ds1/baseboxes# wget "http://puppetlabs.s3.amazonaws.com/pub/Squeeze64.box"
--2012-08-30 21:14:12-- http://puppetlabs.s3.amazonaws.com/pub/Squeeze64.box
Resolving puppetlabs.s3.amazonaws.com... 72.21.215.197
Connecting to puppetlabs.s3.amazonaws.com|72.21.215.197|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-08-30 21:14:12 ERROR 404: Not Found.

Should be:

http://puppetlabs.s3.amazonaws.com/pub/squeeze64.box

Similar to #260, is there any license restrictions on creating Darwin/OSX Vagrant boxes, and then adding them to this list?

The only thing I can think of is the EULA from Apple does say you have to run OS X VMs on Apple hardware.

http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-i386-v20130309.box

Doesn't have /usr/bin/man
Most users expect this to be there, so it would be great if the man package were preinstalled.
Thanks

https://github.com/opscode/bento

The project seems to die slowly, and there is no reason to!
The domain is great, the updates are public, and I believe the only problem kicking ass here is the indexing.

Some columns can be used to make this box list useful (again):

1. Tags (for example, to mark a box unmaintained or archived)
2. Updated (latest boxes?)
3. OS Family (Linux / Windows / BSD-Unix / ChromeOS / OS X / Android-x86 / Other)

My proposed action is to start a 2015 index and drop all other boxes into archive.

The section of www/index.html re: Ubuntu 11.04 should be removed, or updated.