downloading vbox from atlas.hashicorp.com for vagrant

[peter....@gmail.com]

Hello All,

I am beginner in this topic, so please forgive me for my stupid questions. :-)
I am using a server with modified "OS : Ubuntu 14.04.4 LTS" with vagrant and virtualbox packages installed:

dpkg -l|grep vagrant
ii  vagrant                             1.4.3-1                                 all          Tool for building and distributing virtualized development environments

 dpkg -l|grep virtualbox
ii  virtualbox                          4.3.36-dfsg-1+deb8u1ubuntu1.14.04.1     amd64        x86 virtualization solution - base binaries
ii  virtualbox-dkms                     4.3.36-dfsg-1+deb8u1ubuntu1.14.04.1     all          x86 virtualization solution - kernel module sources for dkms
ii  virtualbox-qt                       4.3.36-dfsg-1+deb8u1ubuntu1.14.04.1     amd64        x86 virtualization solution - Qt based user interface

I was able to download from www.vagrantbox.es trusty-server-cloudimg-amd64-vagrant-disk1.box
Official Ubuntu 14.04 daily Cloud Image amd64 (Development release, No Guest Additions)
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

and install it as root:
cd /data/vagrantproject
vagrant box add box1-trusty /data/trusty-server-cloudimg-amd64-vagrant-disk1.box
vagrant up
vagrant ssh

For this box i am able to su to root by using vagrant as password.

NOW:

I am trying to download jessie64 vbox for vagrant use from atlas.hashicorp.com
How can i find links for *.vbox files and their description?

I have found a link for
vagrant init jessie64 https://atlas.hashicorp.com/debian/boxes/jessie64/versions/8.5.0/providers/virtualbox.box
but it gives me error after vagrant up.

Trying:
vagrant init contrib-jessie64 https://atlas.hashicorp.com/debian/boxes/contrib-jessie64/versions/8.5.0/providers/virtualbox.box
this worked - i am even able to ssh to box.
But vagrant as password for 'su -' is not OK. What is the default password in this case?

What is the difference between jessie64 and contrib-jessie64 boxes?
Thanks for the help in advance.
Kind regards,

Ardi

i

[Alvaro Miranda Aguilera]

On Wed, Jul 27, 2016 at 8:22 PM, <peter....@gmail.com> wrote:

debian/boxes/jessie64/versions/8.5.0/providers/

Hello,

For boxes in atlas, after Vagrant 1.5+, you can use  user/box

so you can do

vagrant init -m debian/jessie64

vagrant up

And vagrant will check automatically in atlas, for latest (higher) version and the provider.

Alvaro.

[peter....@gmail.com]

Well, i have used your command and got the following output:

vagrant init -m debian/jessie64
An invalid option was specified. The help for this command
is available below.

Usage: vagrant init [box-name] [box-url]
        --output FILENAME            Output path for the box. '-' for stdout.
    -h, --help                       Print this help

BTW, how do i know which version is downloaded? How can i download a specific version ?
Thanks,
Ardi

[Alvaro Miranda Aguilera]

Hello,

Can you share the output of vagrant version ?

The official installer is here:

https://www.vagrantup.com/downloads.html

Current version is 1.8.5

Thanks

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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/eda1f86c-992c-43e6-b05f-98a5053d4328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[peter....@gmail.com]

As stated in my first mail:

# vagrant --version
Vagrant 1.4.3
# dpkg -l|grep vagrant

ii  vagrant                             1.4.3-1                                 all          Tool for building and distributing virtualized development environments

#

I have seen the 1.8.5 version ready on https://www.vagrantup.com/downloads.html

Is it enough to download the https://releases.hashicorp.com/vagrant/1.8.5/vagrant_1.8.5_x86_64.deb
for debian 64bit and install it as root with 'dpkg -i vagrant_1.8.5_x86_64.deb' over existing version?

Ardi



On Wednesday, 27 July 2016 10:22:11 UTC+2, peter....@gmail.com wrote:

[Alvaro Miranda Aguilera]

IT should.

You can always remove the existing one before.

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 vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/cf98446f-ba4e-4e7c-b0b7-1578e377e534%40googlegroups.com.

[peter....@gmail.com]

Will uninstalling actual version of vagrant remove the already created (now halted) VMs?
I mean whether dir /root/Virtual VMs and directory where I have my projectfiles will NOT be removed during this uninstallation?

Ardi

On Wednesday, 27 July 2016 10:22:11 UTC+2, peter....@gmail.com wrote:

[Alvaro Miranda Aguilera]

Hello,

No VM are deleted when you uninstall or install, and after the upgrade, the vms created should work just fine.

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 vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e7d5955e-7f69-48b6-8001-fe6498f96ead%40googlegroups.com.

[peter....@gmail.com]

Well,

i have installed new version over old one and got the following strange behavior:

1.
At the beginning all the boxes are halted.

2.
###Checking existing version:
#dpkg -l|grep vagrant

ii  vagrant                             1.4.3-1                                 all          Tool for building and distributing virtualized development environments

#

3.
###i have installed new version over old one and got the following strange behavior:
# dpkg -i vagrant_1.8.5_x86_64.deb
(Reading database ... 102890 files and directories currently installed.)
Preparing to unpack vagrant_1.8.5_x86_64.deb ...
Unpacking vagrant (1:1.8.5) over (1:1.8.5) ...
Setting up vagrant (1:1.8.5) ...
#
4.
# vagrant --version
Vagrant 1.8.5
#

5.
# vagrant
Vagrant is upgrading some internal state for the latest version.
Please do not quit Vagrant at this time. While upgrading, Vagrant
will need to copy all your boxes, so it will use a considerable
amount of disk space. After it is done upgrading, the temporary disk
space will be freed.

Press ctrl-c now to exit if you want to remove some boxes or free
up some disk space.

Press the Enter or Return key to continue.^C#

What steps were done wrong?

Ardi



On Wednesday, 27 July 2016 10:22:11 UTC+2, peter....@gmail.com wrote:

[peter....@gmail.com]

Well,
after some minutes it continued and I was able to issue the 'vagrant' command which listed me all available options.
I was able to 'vagrant up' all my vboxes created with older version of vagrant.

But i am still interested, where and what kind of temporary files are created that prevented me to run the new version of vagrant. Is it possible to check these files during upgrade from version "a" to higher version "b"?

I have also seen, that when using: 'vagrant init ubuntu/trusty64
' and 'vagrant up' then after using 'vagrant box list' i see also version number for given box.
Does it appear only when i use the command above or is it due to newer version of vagrant?

Thanks for the explanation in advance.

Ardi

On Wednesday, 27 July 2016 10:22:11 UTC+2, peter....@gmail.com wrote:

[Alvaro Miranda Aguilera]

Hello,

Not sure what can have one wrong.

Over VirtualBox, you should be able to turn on/off the previous VM, and copy/export what you require.

If you could just delete thats in ~/.vagrant.d it should work fine for new boxes.

Word of precauting, work first on the exiting boxes in the Virtualbox gui is the content is portant for you.

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 vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1295fef8-c2a4-48d9-89d9-59f61c3cbb8f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

+31103400555

[peter....@gmail.com]

Thanks for you comments.

Ardi

On Wednesday, 27 July 2016 10:22:11 UTC+2, peter....@gmail.com wrote: