2016-12-04 4 views
1

私は迷惑な人には新しく、WindowsのVirtualBoxを使用してexact64ボックスを設定しようとしています。バグの認証

私が 'vagrant up'を実行すると、VirtualBoxをチェックするとボックスが起動しますが、ログインプロンプトが表示されません。

ここに私の迷路ファイルがあります。

# -*- 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 = "hashicorp/precise64" 
    config.ssh.username = 'vagrant' 
    config.ssh.password = 'vagrant' 
    config.ssh.insert_key = 'true' 

    # 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 
    # apt-get update 
    # apt-get install -y apache2 
    # SHELL 
end 

迷惑メールを実行すると、ここで数分間停止します。

C:\HashiCorp>vagrant up 
Bringing machine 'default' up with 'virtualbox' provider... 
==> default: Checking if box 'hashicorp/precise64' is up to date... 
==> default: Clearing any previously set forwarded ports... 
==> 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: password 

私に次のメッセージを伝えてください。

Timed out while waiting for the machine to boot. This means that 
Vagrant was unable to communicate with the guest machine within 
the configured ("config.vm.boot_timeout" value) time period. 

If you look above, you should be able to see the error(s) that 
Vagrant had when attempting to connect to the machine. These errors 
are usually good hints as to what may be wrong. 

If you're using a custom box, make sure that networking is properly 
working and you're able to connect to the machine. It is a common 
problem that networking isn't setup properly in these boxes. 
Verify that authentication configurations are also setup properly, 
as well. 

If the box appears to be booting properly, you may want to increase 
the timeout ("config.vm.boot_timeout") value. 

注:私は直接ボックスにアクセスした場合、私は「ルート」として ユーザー名でログインすることができませんでしだが、私は、ユーザー名「浮浪者」と パスワード「浮浪者」でログインすることができます。あなたは

config.ssh.username = 'vagrant' 
    config.ssh.password = 'vagrant' 

浮浪者を削除することができます

+0

どのバージョンをやっているのか分からない限り、あなたは

config.ssh.insert_key = 'true' 

を削除することをお勧め?これは万が一1.8.5ではないのですか? –

+0

バグ1.9.0。私はWindows 10を使用していると述べていたはずです。 – Sam

答えて

0

は、それが言及する必要はありませんので、デフォルトのユーザ名であり、それは

(特別に、このボックスに)デフォルトでは、パスワードで秘密鍵で認証していません

あなたはあなたが新しくなったと言っていますので、今はsshキーを気にする必要はありません。私はまた、あなたがベイグラントの

+0

とにかく、 'config.ssh.insert_key = 'true''は1.8以降のデフォルトオプションです。 –

+0

実際、@MattSchuchardは完全に正しいので、デフォルトでは真であり、既定では不浸透性であることについて多くの議論がありました。 Vagrantファイルにデフォルト値を保持するだけで、この行を削除することもできます。 –

+0

ありがとう、私はデフォルトを維持するためにこれらを削除しました。私はまだ残念ながらボックスに自動的にログインするために迷惑メールを取得することで、これ以上の進歩はありません。 – Sam