VVV: hyperv box 'phawxby/trusty64' could not be found

I recently upgraded to Windows 10 Pro and enabled Hyper-V so I could use Docker.

I’ve reviewed https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1082 but the box phawxby/trusty64 that was changed in the Vagrantfile and marked as fixed isn’t accessible from a fresh pull of VVV 2.2.0.

Output is:

Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Box 'phawxby/trusty64' could not be found. Attempting to find and install...
    default: Box Provider: hyperv
    default: Box Version: >= 0
The box 'phawxby/trusty64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/phawxby/trusty64"]
Error: The requested URL returned error: 404 Not Found

If I can, I’d like to stick with VVV for WordPress development as it’s what the rest of my team uses, but I’d also like to be able to run Docker for other projects.

Does anyone have any recommendations? Is there another box that should be used? A different URL? Thanks!

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 17 (11 by maintainers)

Most upvoted comments

Apologies for the delay following up on this.

The problem may not lie with VVV but rather with Vagrant; the failure happens with trying to mount SMB synced folders with HyperV. Output below:

$ vagrant up --provider=hyperv
-f was unexpected at this time.
__   ___   ___   __
\ \ / \ \ / \ \ / / Varying Vagrant Vagrants
 \ V / \ V / \ V /  v2.2.0-
  \_/   \_/   \_/   ☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆☆

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Configured startup memory is 2048
==> default: Configured cpus number is 1
==> default: Importing a Hyper-V instance
    default: Please choose a switch to attach to your Hyper-V instance.
    default: If none of these are appropriate, please open the Hyper-V manager
    default: to create a new virtual switch.
    default:
    default: 1) DockerNAT
    default: 2) Default Switch
    default:
    default: What switch would you like to use? 2
    default: Cloning virtual hard drive...
    default: Creating and registering the VM...
    default: Setting VM Integration Services
    default: Successfully imported a VM with name: Trusty Tahr
==> default: Starting the machine...
==> default: Waiting for the machine to report its IP address...
    default: Timeout: 120 seconds
    default: IP: 172.19.36.185
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 172.19.36.185:22
    default: SSH username: vagrant
    default: SSH auth method: password
    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: Preparing SMB shared folders...
    default: You will be asked for the username and password to use for the SMB
    default: folders shortly. Please use the proper username/password of your
    default: account.
    default:
    default: Username: ******
    default: Password (will be hidden):
Error! Your console doesn't support hiding input. We'll ask for
input again below, but we WILL NOT be able to hide input. If this
is a problem for you, ctrl-C to exit and fix your stdin.
     default: Password (will be hidden): ******

Vagrant requires administator access to create SMB shares and
may request access to complete setup of configured shares.
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: Setting hostname...
==> default: Mounting SMB shared folders...
    default: C:/vvv/www => /srv/www
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t cifs -o sec=ntlmssp,credentials=/etc/smb_creds_vgt-da1f51124d109e262cefba81a712374f-327f087fac3c82b47d8eca185e95a27e,uid=33,gid=1000,dir_mode=0775,file_mode=0774,forceuid,noperm,nobrl,mfsymlinks //10.0.0.45/vgt-da1f51124d109e262cefba81a712374f-327f087fac3c82b47d8eca185e95a27e /srv/www

The error output from the last command was:

mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

See Vagrant issue https://github.com/hashicorp/vagrant/issues/8620 and https://github.com/hashicorp/vagrant/issues/9172. Also seems to be quite a few open issues with HyperV in Vagrant: https://github.com/hashicorp/vagrant/labels/provider%2Fhyperv

I’m inclined to close this issue and give Docker a try instead.

mdecurtins on Feb 16, 2018