Now as I add OSs, I just add lines the same way, those two lines, or is there any additional stuff? On Tuesday, April 2, 2019 at 1:57:15 PM UTC-4, Brian Cain wrote: > > > > On Tue, Apr 2, 2019 at 10:54 AM signmeuptoo <[email protected] > <javascript:>> wrote: > >> thank you, I will work on that information in a bit, I appreciate it. >> Someone else is also helping via email. >> >> One question: >> >> with this part: >> >> c.vm.box = "bento/centos-7.2" >> >> My install via the init box install the box centos term is not >> centos-7.2, but a longer term in the copied and pasted init box. Does it >> know that simpler OS name (centos-7.2)? >> > > Nope, it does not! If you want the bento box specifically, you need the > full name. You can also add and build your own boxes (which means you can > give it any name you want), > but I would consider that an advanced feature that I wouldn't worry about > until learning more and understanding how Vagrant works. > > >> >> >> >> On Tuesday, April 2, 2019 at 1:34:56 PM UTC-4, Brian Cain wrote: >>> >>> Is the problem that you are using a box named "mycentos"? This name >>> should correspond to the box you wish to use, rather than >>> a name you want it to be called. These names typically correspond to >>> boxes on Vagrant Cloud: >>> https://app.vagrantup.com/boxes/search?utf8=%E2%9C%93&sort=downloads&provider=&q=centos >>> >>> So if you wanted to use say, bento/centos-7.2, your Vagrantfile would >>> look like >>> >>> Vagrant.configure("2") do |config| >>> config.vm.provision "shell", inline: "echo Hello" >>> >>> config.vm.define "centos" do |c| >>> c.vm.box = "bento/centos-7.2" >>> end >>> end >>> >>> I also changed the guest to be called "centos". >>> >>> One way to check what name you should type when you run `vagrant up` is >>> the command `vagrant status`. It will show you what names are defined. >>> >>> Since I called this guest "centos", that means you can run `vagrant up >>> centos` and `vagrant ssh centos`, as well as any other vagrant commands for >>> that guest. >>> >>> But more generally, you give your Vagrant guests names through that >>> config option that is `config.vm.define`. The string after this is the name. >>> >>> Have you started with the introduction/getting started guide on the >>> website? https://www.vagrantup.com/intro/getting-started/index.html >>> >>> I recommend following along and reading through all of that. It should >>> give you a good understanding of how to use Vagrant and what steps you >>> might be missing. >>> >>> Thanks! >>> >>> On Tue, Apr 2, 2019 at 10:23 AM signmeuptoo <[email protected]> wrote: >>> >>>> >>>> May I give some background: I tried installing centos via vangrant init >>>> <my_filename> <the_file_on_the_vagrant_site> Several times. This I messed >>>> with over a few days. I'm a greenhorn as they say doing self study. >>>> >>>> I ended up, it now seems with a vagrant and a vagrant2 directory, a >>>> .vagrant and a .vangrant.d directory. >>>> >>>> It seems that that is part of the problem. >>>> >>>> Something seems to have gone wrong with the init process of the install. >>>> >>>> I tried chosing these names: centos, centos1, centos2, CentOS, and OS1. >>>> >>>> It only would start up with vagrant up, then ssh vagrant default >>>> (rather than any of the names I tried), and that is before I recently >>>> tried >>>> to change the Vagrantfile as per someone's guidance. I'm still in a >>>> quandry >>>> whether to start from the beginnning and if so, how to do so. >>>> >>>> On Monday, April 1, 2019 at 7:10:35 PM UTC-4, signmeuptoo 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? >>>>> >>>>> 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]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/8f19b149-6436-4fbd-85d9-401163712904%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/8f19b149-6436-4fbd-85d9-401163712904%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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/94e2d3f4-5c30-4a9d-93d2-43d3c1703a48%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/94e2d3f4-5c30-4a9d-93d2-43d3c1703a48%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/c3a68d05-c5d3-497f-89db-46c05922d71b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
