Bertrand Sirodot
Bertrand Sirodot
Hi, when you created your centos7_template, did you download the vagrant.pub key, put it into the authorized_keys file and configured sshd accordingly? I had that issue when I first started...
@gaga-github : did you change the settings in your /etc/ssh/sshd_config file to use the authorized_keys file?
@bala-janakiraman you are correct that you need to update the /etc/ssh/sshd_config. Here is what you need to change: ``` PubKeyAuthentication yes AuthorizedKeysFile %h/.ssh/authorized_keys PermitEmptyPasswords no ``` Once you've changed those...
@bala-janakiraman Did it work for you?
I think it would be good if the default behaviour was the same on all providers, whether the builds are done in parallel or not. I think having this sort...
Hi, this is the way I have been doing this: ``` jupiter = { 'name' => "jupiter", 'ip' => "192.168.1.141" } mars = { 'name' => "mars", 'ip' => "192.168.1.142"...
I am running into the same issue. The reason for this is that the template for the setup credentials job doesn't include any key inheriting its value from the `values.yaml`...