The box 'ubuntu/vivid64' could not be found about fopnp

[brandon-rhodes]

I guess I will have to switch to another version of Linux! Thanks for letting me know; I will try to get to this some time in November.

[brandon-rhodes]

I just got the chance to try this myself, and it worked without any error.

$ vagrant init brandon-rhodes/playground                                                                                                                                   ~/t2 
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
$ vagrant up --provider virtualbox                                                                                                                                         ~/t2 
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'brandon-rhodes/playground'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'brandon-rhodes/playground' is up to date...
==> default: Setting the name of the VM: t2_default_1478657836488_73139
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 4.3.26
    default: VirtualBox Version: 5.0
==> default: Mounting shared folders...
    default: /vagrant => /home/brandon/t2
$ vagrant ssh                                                                                                                                                              ~/t2 
Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-25-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Wed Nov  9 02:18:04 UTC 2016

  System load:  0.29              Processes:           77
  Usage of /:   6.0% of 38.81GB   Users logged in:     0
  Memory usage: 36%               IP address for eth0: 10.0.2.15
  Swap usage:   0%

  Graph this data and manage this system at:
    https://landscape.canonical.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

New release '15.10' available.
Run 'do-release-upgrade' to upgrade to it.


vagrant@vagrant-ubuntu-vivid-64:~$

Could you try again and see whether it was maybe a transient network error that caused your problem?

[brandon-rhodes]

I am going to close this issue for now since the command succeeded for me, but if you are able to try again and it is still broken then feel free to re-open and we can try further steps to track down why it cannot find that box for you.