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

Use bento prefix for box names in README #445

Merged
merged 1 commit into from
Sep 13, 2015
Merged

Conversation

leejones
Copy link
Contributor

First up, thanks for bento! I've used these boxes for a while now and really appreciate the effort that goes into this project ✨.

I ran into a small issue, but I think I have a solution. vagrant up failed when I used the chef/ prefix in my Vagrantfile.

Here is the error I experienced:

$> vagrant --version
Vagrant 1.7.4
$> cat Vagrantfile
Vagrant.configure(2) do |config|
  config.vm.box = "chef/ubuntu-12.04"
end
$> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'chef/ubuntu-12.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'chef/ubuntu-12.04'
    default: URL: https://atlas.hashicorp.com/chef/ubuntu-12.04
The box you're adding has a name different from the name you
requested. For boxes with metadata, you cannot override the name.
If you're adding a box using `vagrant box add`, don't specify
the `--name` parameter. If the box is being added via a Vagrantfile,
change the `config.vm.box` value to match the name below.

Requested name: chef/ubuntu-12.04
Actual name: bento/ubuntu-12.04

I updated the README based on the recommendation in the error message. The bento/ prefix works in my testing for both vagrant up and vagrant box add.

vagrant box add works with the chef/ prefix because it appears to redirect from the chef/ prefix to the bento/ one. I updated the vagrant box add example to use the bento/ prefix since it seems to be the new location and for consistency between the two examples.

`vagrant up` failed when I used the `chef/` prefix in my `Vagrantfile`.

Here is the error I experienced:

```
$> vagrant --version
Vagrant 1.7.4
$> cat Vagrantfile
Vagrant.configure(2) do |config|
  config.vm.box = "chef/ubuntu-12.04"
end
$> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'chef/ubuntu-12.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'chef/ubuntu-12.04'
    default: URL: https://atlas.hashicorp.com/chef/ubuntu-12.04
The box you're adding has a name different from the name you
requested. For boxes with metadata, you cannot override the name.
If you're adding a box using `vagrant box add`, don't specify
the `--name` parameter. If the box is being added via a Vagrantfile,
change the `config.vm.box` value to match the name below.

Requested name: chef/ubuntu-12.04
Actual name: bento/ubuntu-12.04
```

I updated the README based on the recommendation in the error message. The `bento/` prefix works in my testing for both `vagrant up` and `vagrant box add`. 

`vagrant box add` works with the `chef/` prefix because it appears to redirect from the `chef/` prefix to the `bento/` one. I updated the `vagrant box add` example to use the `bento/` prefix since it seems to be the new location and for consistency between the two examples.
@cheeseplus
Copy link
Contributor

Just missed this when we were updating - +1

cheeseplus pushed a commit that referenced this pull request Sep 13, 2015
Use bento prefix for box names in README
@cheeseplus cheeseplus merged commit 2a5df73 into chef:master Sep 13, 2015
@leejones leejones deleted the patch-1 branch September 15, 2015 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants