質問編集履歴

2

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

2016/05/06 05:06

投稿

退会済みユーザー
test CHANGED
File without changes
test CHANGED
@@ -123,3 +123,155 @@
123
123
  from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'
124
124
 
125
125
  ```
126
+
127
+
128
+
129
+
130
+
131
+ ###vagrantfileの中身
132
+
133
+ ```
134
+
135
+ # -*- mode: ruby -*-
136
+
137
+ # vi: set ft=ruby :
138
+
139
+
140
+
141
+ # All Vagrant configuration is done below. The "2" in Vagrant.configure
142
+
143
+ # configures the configuration version (we support older styles for
144
+
145
+ # backwards compatibility). Please don't change it unless you know what
146
+
147
+ # you're doing.
148
+
149
+ Vagrant.configure(2) do |config|
150
+
151
+ # The most common configuration options are documented and commented below.
152
+
153
+ # For a complete reference, please see the online documentation at
154
+
155
+ # https://docs.vagrantup.com.
156
+
157
+
158
+
159
+ # Every Vagrant development environment requires a box. You can search for
160
+
161
+ # boxes at https://atlas.hashicorp.com/search.
162
+
163
+ config.vm.box = "centos6"
164
+
165
+
166
+
167
+ # Disable automatic box update checking. If you disable this, then
168
+
169
+ # boxes will only be checked for updates when the user runs
170
+
171
+ # `vagrant box outdated`. This is not recommended.
172
+
173
+ # config.vm.box_check_update = false
174
+
175
+
176
+
177
+ # Create a forwarded port mapping which allows access to a specific port
178
+
179
+ # within the machine from a port on the host machine. In the example below,
180
+
181
+ # accessing "localhost:8080" will access port 80 on the guest machine.
182
+
183
+ # config.vm.network "forwarded_port", guest: 80, host: 8080
184
+
185
+
186
+
187
+ # Create a private network, which allows host-only access to the machine
188
+
189
+ # using a specific IP.
190
+
191
+ # config.vm.network "private_network", ip: "192.168.33.10"
192
+
193
+
194
+
195
+ # Create a public network, which generally matched to bridged network.
196
+
197
+ # Bridged networks make the machine appear as another physical device on
198
+
199
+ # your network.
200
+
201
+ # config.vm.network "public_network"
202
+
203
+
204
+
205
+ # Share an additional folder to the guest VM. The first argument is
206
+
207
+ # the path on the host to the actual folder. The second argument is
208
+
209
+ # the path on the guest to mount the folder. And the optional third
210
+
211
+ # argument is a set of non-required options.
212
+
213
+ # config.vm.synced_folder "../data", "/vagrant_data"
214
+
215
+
216
+
217
+ # Provider-specific configuration so you can fine-tune various
218
+
219
+ # backing providers for Vagrant. These expose provider-specific options.
220
+
221
+ # Example for VirtualBox:
222
+
223
+ #
224
+
225
+ # config.vm.provider "virtualbox" do |vb|
226
+
227
+ # # Display the VirtualBox GUI when booting the machine
228
+
229
+ # vb.gui = true
230
+
231
+ #
232
+
233
+ # # Customize the amount of memory on the VM:
234
+
235
+ # vb.memory = "1024"
236
+
237
+ # end
238
+
239
+ #
240
+
241
+ # View the documentation for the provider you are using for more
242
+
243
+ # information on available options.
244
+
245
+
246
+
247
+ # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
248
+
249
+ # such as FTP and Heroku are also available. See the documentation at
250
+
251
+ # https://docs.vagrantup.com/v2/push/atlas.html for more information.
252
+
253
+ # config.push.define "atlas" do |push|
254
+
255
+ # push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
256
+
257
+ # end
258
+
259
+
260
+
261
+ # Enable provisioning with a shell script. Additional provisioners such as
262
+
263
+ # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
264
+
265
+ # documentation for more information about their specific syntax and use.
266
+
267
+ # config.vm.provision "shell", inline: <<-SHELL
268
+
269
+ # sudo apt-get update
270
+
271
+ # sudo apt-get install -y apache2
272
+
273
+ # SHELL
274
+
275
+ end
276
+
277
+ ```

1

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

2016/05/06 05:06

投稿

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