为什么Chocolatey不能安装在此Vagrant盒子上? [英] Why does Chocolatey not install on this Vagrant box?

问题描述

我已使用powershell设置在主机(Windows)上安装了Chocolatey:

I've installed chocolatey on my host machine (windows) using the powershell provision:

 Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

这一切都很好，choco可以在主机上工作，但是当我尝试通过VM中的 vagrant ssh 安装它时，它根本无法工作.我尝试使用脚本并将其添加到vagrantfile中，但是没有运气.

This is all fine and choco works on the host machine, but when I try to install it via vagrant sshin the VM, it doesn't work at all. I've tried using scripts and adding them into the vagrantfile but with no luck.

如何在Windows Vagrant VM上获取巧克力味?

我的流浪文件

# -*- 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 = "kensykora/windows_2012_r2_standard"

  # 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: 22, host: 2200

  # 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.11"

  # 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
  # chocolatey:
  config.vm.provision :shell, path: "InstallChocolatey.ps1"
  # 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
  Vagrant.configure("2") do |config|
  config.vm.provision "shell", path: "C:\Users\WorkExperience\Desktop\Working on Vagrant\WindowsServer2012-vagrant\shell\main.cmd"
  end
end

installchocolatey.ps1文件:

 $ChocoInstallPath = "$env:SystemDrive\ProgramData\Chocolatey\bin"

  if (!(Test-Path $ChocoInstallPath)) {
      iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
  }

任何帮助，不胜感激.

推荐答案

您实际上在主configure块中是否有一个重复的configure块，围绕该配置方法?如果是这样，我怀疑这是有效的Ruby代码，但是实际上没有正确配置Vagrant.

Do you actually have a duplicate configure block inside the main configure block, surrounding the provision method? If so, I suspect that this is valid Ruby code, but Vagrant is effectively not configured properly.

Vagrant.configure("2") do |config|
  config.vm.provision "shell", path: "C:\Users\WorkExperience\Desktop\Working on Vagrant\WindowsServer2012-vagrant\shell\main.cmd"
end

我将删除该多余的configure块，仅保留

I would remove that extra configure block and leave only this

config.vm.provision "shell", path: "C:\Users\WorkExperience\Desktop\Working on Vagrant\WindowsServer2012-vagrant\shell\main.cmd"

您是否从 vagrant up 输出了调试/详细日志?

Do you have a debug/verbose log output from vagrant up?

此外，在Vagrant的1.8.x +版本中，设置:powershell_elevated_interactive =>可能对您有所帮助.true 作为 config.vm.provision:shell 的选项之一.不知道这是否会与 .cmd 和 .bat 文件有所不同，但是对于PowerShell，它确保仍与桌面交互，从而解决了可能发生的一些问题.与需要交互式运行的安装程序有关(即使它们无人值守/无提示).

Also, you may find it helpful in versions 1.8.x+ of Vagrant to set :powershell_elevated_interactive => true as one of the options for config.vm.provision :shell. Not sure if this will make a difference with .cmd and .bat files, but for PowerShell it ensures it is still interactive with the desktop, which resolves some issues that can occur related to installers needing to be running interactively (even when they are unattended/silent).

这篇关于为什么Chocolatey不能安装在此Vagrant盒子上?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！