5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
60 lines
2.4 KiB
Markdown
60 lines
2.4 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Boxes"
|
|
sidebar_current: "boxes"
|
|
description: |-
|
|
Boxes are the package format for Vagrant environments. A box can be used by
|
|
anyone on any platform that Vagrant supports to bring up an identical
|
|
working environment.
|
|
---
|
|
|
|
# Boxes
|
|
|
|
Boxes are the package format for Vagrant environments. A box can be used by
|
|
anyone on any platform that Vagrant supports to bring up an identical
|
|
working environment.
|
|
|
|
The `vagrant box` utility provides all the functionality for managing
|
|
boxes. You can read the documentation on the [vagrant box](/docs/cli/box.html)
|
|
command for more information.
|
|
|
|
The easiest way to use a box is to add a box from the
|
|
[publicly available catalog of Vagrant boxes](https://atlas.hashicorp.com/boxes/search).
|
|
You can also add and share your own customized boxes on this website.
|
|
|
|
Boxes also support versioning so that members of your team using Vagrant
|
|
can update the underlying box easily, and the people who create boxes
|
|
can push fixes and communicate these fixes efficiently.
|
|
|
|
You can learn all about boxes by reading this page as well as the
|
|
sub-pages in the navigation to the left.
|
|
|
|
## Discovering Boxes
|
|
|
|
The easiest way to find boxes is to look on the
|
|
[public Vagrant box catalog](https://atlas.hashicorp.com/boxes/search)
|
|
for a box matching your use case. The catalog contains most major operating
|
|
systems as bases, as well as specialized boxes to get you up and running
|
|
quickly with LAMP stacks, Ruby, Python, etc.
|
|
|
|
The boxes on the public catalog work with many different
|
|
[providers](/docs/providers/). Whether you are using Vagrant with
|
|
VirtualBox, VMware, AWS, etc. you should be able to find a box you need.
|
|
|
|
Adding a box from the catalog is very easy. Each box shows you instructions
|
|
with how to add it, but they all follow the same format:
|
|
|
|
```
|
|
$ vagrant box add USER/BOX
|
|
```
|
|
|
|
For example: `vagrant box add hashicorp/precise64`. You can also quickly
|
|
initialize a Vagrant environment with `vagrant init hashicorp/precise64`.
|
|
|
|
~> **Namespaces do not guarantee canonical boxes!** A common misconception is
|
|
that a namespace like "ubuntu" represents the canonical space for Ubuntu boxes.
|
|
This is untrue. Namespaces on Atlas behave very similarly to namespaces on
|
|
GitHub, for example. Just as GitHub's support team is unable to assist with
|
|
issues in someone's repository, HashiCorp's support team is unable to assist
|
|
with third-party published boxes.
|