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, [email protected] wrote:
>
> 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 
>
>
>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/d150623c-8bbc-47fd-926c-38ae163764df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to