# -*- 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|
 config.vm.provision "shell", inline: "echo Hello"

 config.vm.define :OS1 do |os1|
   os1.vm.box = "mycentos"
 end

  # 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://vagrantcloud.com/search.


  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  # config.vm.box_url = 
"https://github.com/tommy-muehle/puppet-vagrant-boxes/releases/download/1.1.0/centos-7.0-x86_64.box";
  
  # 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.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: 
"127.0.0.1"

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

  # 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

On Tuesday, April 2, 2019 at 11:52:46 AM UTC-4, Brian Cain wrote:
>
> Hey there!
>
> On Mon, Apr 1, 2019 at 4:10 PM signmeuptoo <[email protected] 
> <javascript:>> wrote:
>
>> Hi, I'm a vagrant noobie who is in self study for Linux Admin theory.
>>
>> I run Linux Mint, not Windows, in case that is germane to my problems.
>>
>> I performed a few installs of VBs of centos for personal study with 
>> vagrant, however, after trying several times, and not getting ssh to load 
>> the OSs by the names I used during installs, I gave up for a bit and 
>> searched all over and found out that vagrant ssh default (or not using 
>> default) allowed the VM to be accessable.
>>
>> However, I want to be able to vagrant up multiple OSs on my system that 
>> already had VirtualBox installed, and have them ssh able with the names I 
>> give them, rather than default as a name. I've read documentation but I am 
>> a bit lost because my aptitude isn't up to speed with the explanations 
>> given on vagrant's site, I don't understand them yet.
>>
>> In my .vagrant.d home directory (there is also a .vagrant directory) I 
>> find 5 VMs listed, with names such as centos1 and such. I tried changing 
>> names of the directories but that didn't do the trick.
>>
>> Is there a change I need to make to my Vagrantfile and also how do I 
>> install additional versions of Centos, Debian, and SUSE?  
>>
>
> I recommend sharing what your Vagrantfile looks like first so we can 
> understand what exactly you are working with.
>
> Thanks!
>  
>
>>
>> My apologies for being a greenhorn, I'm trying to learn as well as I can.
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/0cc56797-f19a-48d9-8722-bd7b0ade09e2%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/0cc56797-f19a-48d9-8722-bd7b0ade09e2%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Brian Cain
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/a0384298-0089-478d-a4d6-7ddd78833c72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to