Hello THE Vagrant way is to add the known vagrant public ssh key, that will be replaced on first on first boot.
So, if you are starting with a box that you will repackage the best is to add config.ssh.insert_key = false to that intermediate box, so the ssh key won't be replaced. Alvaro. On Mon, Aug 28, 2017 at 1:41 PM, James Newton <[email protected]> wrote: > Hello helpful Vagrant experts! > > I'm new to Vagrant, so I'm taking baby steps to make sure that I > understand the process. I want to ensure that I can create a custom package > before I start doing any serious development in the virtual machine. > > I've created a custom Vagrant package, and I am having an issue with `vagrant > ssh`, where it asks for a password: > > $ vagrant ssh > ==> default: The machine you're attempting to SSH into is configured to use > ==> default: password-based authentication. Vagrant can't script entering > the > ==> default: password for you. If you're prompted for a password, please > enter > ==> default: the same password you have configured in the Vagrantfile. > [email protected]'s password: | > > There is no such request from the customized box from which the package > was made. > > On my development machine, the username and password are set in the file > at `home/blackslate/.vagrant.d/boxes/nginx/0/virtualbox/ > include/_Vagrantfile`: > > # Front load the includes > include_vagrantfile = File.expand_path("../include/_Vagrantfile", > __FILE__) > load include_vagrantfile if File.exist?(include_vagrantfile) > > Vagrant.configure("2") do |config| > config.vm.base_mac = "022185D04910" > *config.ssh.username = "ubuntu"* > * config.ssh.password = "27f8dbe40a2e195f6bd6434a"* > > config.vm.provider "virtualbox" do |vb| > vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ] > vb.customize [ "modifyvm", :id, "--uartmode1", "file", > File.join(Dir.pwd, "ubuntu-xenial-16.04-cloudimg-console.log") ] > end > end > > > The username/password appear to be used correctly during the `vagrant up` > process, but are not being accessed during `vagrant ssh`. I have posted a > question about this on StackOverflow > <https://stackoverflow.com/q/45903812/1927589>. It would probably be best > to discuss the issue there, and to report back in this thread when the > issue has been resolved. > > Thanks in advance for any enlightenment that you can give me, > > James > > -- > 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/76aefa2d-18c0-413e-915b-db52f615a9cf%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/76aefa2d-18c0-413e-915b-db52f615a9cf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- 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/CAHqq0ew6DHEw2snf23wOO%2BpA0nrOexDR6vxiAfbX_1E%2B8WehMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
