unable to vagrant up with newly created box from packer

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

unable to vagrant up with newly created box from packer

Jungsuk Lee
I think i found a bug in Vagrant.

When I converted an AMI in AWS into vagrant box, the artifact was successfully created.
So I could get vagrant box for the image in AWS.

But When I execute 

vagrant box add odoo/path/to/box ----> successfully added

vagrant init odoo----> Vagrantfile successfully created 

vagrant up ----> here is an error

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'odoo' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'odoo' (v0) for provider: virtualbox
    default: Downloading: odoo
    default:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Couldn't open file /C:/Users/Administrator/Desktop/Odoo/vagrant_odoo_theme/odoo

Is there any solution for this bug?

Thanks

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/a6504e95-d7b2-4764-850b-19233095b4bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: unable to vagrant up with newly created box from packer

Alvaro Miranda Aguilera

On Fri, Apr 28, 2017 at 9:54 AM, Jungsuk Lee <[hidden email]> wrote:
vagrant up ----> here is an error

is not a bug.

by default, vagrant will use virtualbox.

2 options.

one, use vagrant up --provider aws

two, add this to your project.

config.vm.provider "aws"

Alvaro.

--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez7uuPgSYLPZHv1X%2B-a0iXqHb8GPX-CQXqsYMuHt5HRPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.