Re: [vagrant-up] Old ubuntu/xenial64 box version points to current

[Alvaro Miranda Aguilera]

Hello

Thats how canonical manage their boxes in vagrant cloud

What I did once was create my own boxes pointing to those, however there is
no guarantee the old boxes will stay for ever.
Other option is just create your own boxes.

https://github.com/cbednarski/packer-ubuntu

Alvaro.

On Wed, Feb 14, 2018 at 5:34 AM, Pavel Martynov  wrote:

> Hi everyone!
>
> I found that I can not download old version of
> ubuntu/xenial64 20171028.0.0. If I do "vagrant.exe box add ubuntu/xenial
> --box-version 20171028.0.0", then vagrant downloads box to
> ~/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20171028.0.0/virtualbox/,
> but in box.ovf will be line " ovf:id="ubuntu-xenial-16.04-cloudimg-20171028">".
> Look at versions mismatch.
>
> Additionally, I test download with curl:
>
> $ curl -X HEAD -i https://vagrantcloud.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> HTTP/1.1 302 Found
> 
> Location: https://app.vagrantup.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> 
>
> $ curl -X HEAD -i https://app.vagrantup.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> 
> Location: http://cloud-images.ubuntu.com/xenial/current/xenial-
> server-cloudimg-amd64-vagrant.box
> 
>
> So, https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20171028.0.0/
> providers/virtualbox.box actually points to "current", which is 20171028
> now.
> This is a bug or expected behavior?
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/3d81a39f-edc6-4476-b394-4d38f66d76b8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exL59CiQ034diGCRUZczowXH8eW%3DJHi%2BRbAjgOb8LCP_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Old ubuntu/xenial64 box version points to current

[Pavel Martynov]

Hi everyone!

I found that I can not download old version of 
ubuntu/xenial64 20171028.0.0. If I do "vagrant.exe box add ubuntu/xenial 
--box-version 20171028.0.0", then vagrant downloads box to 
~/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20171028.0.0/virtualbox/, 
but in box.ovf will be line "". Look at versions mismatch.

Additionally, I test download with curl:

$ curl -X HEAD -i 
https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20171028.0.0/providers/virtualbox.box
HTTP/1.1 302 Found

Location: 
https://app.vagrantup.com/ubuntu/boxes/xenial64/versions/20171028.0.0/providers/virtualbox.box


$ curl -X HEAD -i 
https://app.vagrantup.com/ubuntu/boxes/xenial64/versions/20171028.0.0/providers/virtualbox.box

Location: 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box


So, 
https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20171028.0.0/providers/virtualbox.box
 
actually points to "current", which is 20171028 now.
This is a bug or expected behavior?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/3d81a39f-edc6-4476-b394-4d38f66d76b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.