teratail header banner
teratail header banner
質問するログイン新規登録

質問編集履歴

2

vagrantfileの内容を追加しました。

2016/05/06 05:06

投稿

退会済みユーザー
title CHANGED
File without changes
body CHANGED
@@ -60,4 +60,80 @@
60
60
  from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout'
61
61
  from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/communicators/ssh/communicator.rb:42:in `wait_for_ready'
62
62
  from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'
63
+ ```
64
+
65
+
66
+ ###vagrantfileの中身
67
+ ```
68
+ # -*- mode: ruby -*-
69
+ # vi: set ft=ruby :
70
+
71
+ # All Vagrant configuration is done below. The "2" in Vagrant.configure
72
+ # configures the configuration version (we support older styles for
73
+ # backwards compatibility). Please don't change it unless you know what
74
+ # you're doing.
75
+ Vagrant.configure(2) do |config|
76
+ # The most common configuration options are documented and commented below.
77
+ # For a complete reference, please see the online documentation at
78
+ # https://docs.vagrantup.com.
79
+
80
+ # Every Vagrant development environment requires a box. You can search for
81
+ # boxes at https://atlas.hashicorp.com/search.
82
+ config.vm.box = "centos6"
83
+
84
+ # Disable automatic box update checking. If you disable this, then
85
+ # boxes will only be checked for updates when the user runs
86
+ # `vagrant box outdated`. This is not recommended.
87
+ # config.vm.box_check_update = false
88
+
89
+ # Create a forwarded port mapping which allows access to a specific port
90
+ # within the machine from a port on the host machine. In the example below,
91
+ # accessing "localhost:8080" will access port 80 on the guest machine.
92
+ # config.vm.network "forwarded_port", guest: 80, host: 8080
93
+
94
+ # Create a private network, which allows host-only access to the machine
95
+ # using a specific IP.
96
+ # config.vm.network "private_network", ip: "192.168.33.10"
97
+
98
+ # Create a public network, which generally matched to bridged network.
99
+ # Bridged networks make the machine appear as another physical device on
100
+ # your network.
101
+ # config.vm.network "public_network"
102
+
103
+ # Share an additional folder to the guest VM. The first argument is
104
+ # the path on the host to the actual folder. The second argument is
105
+ # the path on the guest to mount the folder. And the optional third
106
+ # argument is a set of non-required options.
107
+ # config.vm.synced_folder "../data", "/vagrant_data"
108
+
109
+ # Provider-specific configuration so you can fine-tune various
110
+ # backing providers for Vagrant. These expose provider-specific options.
111
+ # Example for VirtualBox:
112
+ #
113
+ # config.vm.provider "virtualbox" do |vb|
114
+ # # Display the VirtualBox GUI when booting the machine
115
+ # vb.gui = true
116
+ #
117
+ # # Customize the amount of memory on the VM:
118
+ # vb.memory = "1024"
119
+ # end
120
+ #
121
+ # View the documentation for the provider you are using for more
122
+ # information on available options.
123
+
124
+ # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
125
+ # such as FTP and Heroku are also available. See the documentation at
126
+ # https://docs.vagrantup.com/v2/push/atlas.html for more information.
127
+ # config.push.define "atlas" do |push|
128
+ # push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
129
+ # end
130
+
131
+ # Enable provisioning with a shell script. Additional provisioners such as
132
+ # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
133
+ # documentation for more information about their specific syntax and use.
134
+ # config.vm.provision "shell", inline: <<-SHELL
135
+ # sudo apt-get update
136
+ # sudo apt-get install -y apache2
137
+ # SHELL
138
+ end
63
139
  ```

1

質問内容をより詳細に記述しました。

2016/05/06 05:06

投稿

退会済みユーザー
title CHANGED
File without changes
body CHANGED
@@ -1,11 +1,26 @@
1
1
  ###前提・実現したいこと
2
- 下記のようにvagrant upで成功ているのですが、virtualboxを開くと現在稼働中の仮想マシンリストに何も表示されません。このようなケースでどのような原因が考えられますでしょうか
2
+ vagrant upのですが、virtualboxを開くと現在稼働中の仮想マシンリストに何も表示されません。どのような原因が考えられますでしょうか
3
3
 
4
+ ###vagrantbox.esより入手したbox
5
+ CentOS 6.6 x64 (Minimal, VirtualBox Guest Additions, Puppet 3.7.5 - see here for more infos)
6
+
7
+ ###vagrant statusの結果
4
8
  ```
9
+ default not created (virtualbox)
10
+
11
+ The environment has not yet been created. Run `vagrant up` to
12
+ create the environment. If a machine is not created, only the
13
+ default provider will be shown. So if a provider is not listed,
14
+ then the machine is not created for that environment.
15
+ ```
16
+
17
+
18
+ ###vagrant upの結果
19
+ ```
5
20
  Bringing machine 'default' up with 'virtualbox' provider...
6
- ==> default: Importing base box 'centOS'...
21
+ ==> default: Importing base box 'centos6'...
7
22
  ==> default: Matching MAC address for NAT networking...
8
- ==> default: Setting the name of the VM: centOS_default_1462504339155_49355
23
+ ==> default: Setting the name of the VM: centos_default_1462506844291_40907
9
24
  ==> default: Clearing any previously set forwarded ports...
10
25
  ==> default: Clearing any previously set network interfaces...
11
26
  ==> default: Preparing network interfaces based on configuration...