找不到框"laravel/homestead" [英] Box 'laravel/homestead' could not be found

查看:70
本文介绍了找不到框"laravel/homestead"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经从此处手动下载了laravel/homestead框.

I have downloaded the laravel/homestead box manually from here.

我成功添加了该框:

vagrant box add file:///path/to/the/laravel/homestead.box --name 'laravel/homestead'

但是当我运行vagrant up时,它会说:Box 'laravel/homestead' could not be found,即使vagrant box list显示了该框.

but when I run vagrant up it says: Box 'laravel/homestead' could not be found even though vagrant box list shows the box.

下载页面显示运行vagrant init laravel/homestead会生成vagrantfile,但是laravel/homestead存储库本身会提供vagrantfile.

The download page says that run vagrant init laravel/homestead that generates a vagrantfile but the laravel/homestead repository itself provides a vagrantfile.

我可以使用vagrant init laravel/homestead生成的vagrantfile进行vagrant up,但是它缺少laravel/homestead存储库的vagrantfile内部的必要配置.

I can vagrant up with the vagrantfile that is generated with vagrant init laravel/homestead but it lacks the essential configs inside the laravel/homestead repository's vagrantfile.

这是生成的vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "laravel/homestead"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   sudo apt-get update
  #   sudo apt-get install -y apache2
  # SHELL
end

它具有以下设置:

Vagrant.configure(2) do |config|  
    config.vm.box = "laravel/homestead"
end

我试图将其添加到默认的laravel/homesteadvagrantfile中,但是没有用.

I tried to add this to the default laravel/homestead's vagrantfile but it didn't work.

require 'json'
require 'yaml'

VAGRANTFILE_API_VERSION = "2"
confDir = $confDir ||= File.expand_path("~/.homestead")

homesteadYamlPath = confDir + "/Homestead.yaml"
homesteadJsonPath = confDir + "/Homestead.json"
afterScriptPath = confDir + "/after.sh"
aliasesPath = confDir + "/aliases"

require File.expand_path(File.dirname(__FILE__) + '/scripts/homestead.rb')

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
    if File.exists? aliasesPath then
        config.vm.provision "file", source: aliasesPath, destination: "~/.bash_aliases"
    end

    if File.exists? homesteadYamlPath then
        Homestead.configure(config, YAML::load(File.read(homesteadYamlPath)))
    elsif File.exists? homesteadJsonPath then
        Homestead.configure(config, JSON.parse(File.read(homesteadJsonPath)))
    end

    if File.exists? afterScriptPath then
        config.vm.provision "shell", path: afterScriptPath
    end

    ## HERE I added the setting ############################################
    config.vm.box = "laravel/homestead"
    ########################################################################
end

我该怎么办?

推荐答案

laravel/homstead项目vagrant init

laravel/homstead项目提供的Vagrant文​​件使用一些ruby代码来帮助设置流浪者环境.从宅基红宝石代码中可以看到的是检查您是否有一个框的版本大于或等于0.4.0:

The Vagrantfile provided by the laravel/homstead project uses some ruby code to assist in setting up the vagrant environment. What we can see from the homestead ruby code is that it is checking that you have a box with a version greater than or equal to 0.4.0:

config.vm.box_version = settings["version"] ||= ">= 0.4.0"

当您手动添加该框时,您会发现它在本地计算机上存在:

As you added the box manually you will see that it is present on your local machine:

$ vagrant box list
laravel/homestead               (virtualbox, 0)

但是请注意,提供者旁边的数字是0.该数字是包装盒的版本.由于是手动添加框,因此框元数据不可用,默认情况下,您将获得版本0.

Note however the number next to the provider is 0. That number is the box version. As the box was added manually the box metadata was not available and by default you will get a version of 0.

当您现在执行vagrant up时,代码正在检查是否有> = 0.4.0的框,而您没有该框,这就是为什么得到Box 'laravel/homestead' could not be found的原因.然后,它将尝试以所需的最低版本下载该框.

When you now do a vagrant up the code is checking if you have a box >= 0.4.0 which you don't have so is why you are getting Box 'laravel/homestead' could not be found. It would then attempt to download the box at the minimal version required.

要避免这种情况,您可以在与下载的盒子文件相同的目录中本地创建一个metadata.json文件.例如:

To circumvent around this you could create a metadata.json file locally in the same directory as your downloaded box file. e.g:

{
    "name": "laravel/homestead",
    "versions": [{
        "version": "0.4.0",
        "providers": [{
            "name": "virtualbox",
            "url": "file:///path/to/homestead.box"
        }]
    }]
}

然后运行vagrant box add metadata.json

这将为包装盒安装一个版本,可以通过以下方式确认:

This will install the box with a version and can be confirmed by:

$ vagrant box list
laravel/homestead               (virtualbox, 0.4.0)

您现在可以使用本地框执行vagrant up.

You will now be able to perform vagrant up using your local box.

这篇关于找不到框"laravel/homestead"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆