> > >> I'm asking for the `vagrant` user to not be created and instead a user >> account with a configurable name to be employed and used instead for all >> other interactions with the vm (provisioning, login, etc). >> > Typical Vagrant baseboxes come with preinstalled `vagrant` user (with default insecure public key), but you can build your own vagrant box (e.g. with Packer) with the predefined user(s) you want. Note that I am not sure where it could really help to do so...
> >> Is it possible to have Vagrant establish a vm and invoke provisioning >> (Ansible) with a username other than `vagrant`? >> > Alvaro: if you specify a new user with config.ssh.username then you can use that other user and not have vagrant user at all.. Alvaro's comment is fully correct, but you have to be aware that some Ansible settings can bypass Vagrant's `config.ssh.username`. See "WHY DOES THE ANSIBLE PROVISIONER CONNECT AS THE WRONG USER?" section at the end of http://docs.vagrantup.com/v2/provisioning/ansible.html. It also means that you can use these settings to control the ansible provisioning user... -- 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]. For more options, visit https://groups.google.com/d/optout.
