Hot answers tagged

1

You can try adding your passphrase to the keychain using ssh-add -K, this will ask you the passphrase for the first time and later on it won't ask.


1

Passphrase is defined by the way you created your private key. When creating a key pair you need to opt for no passphrase on the private key - this should solve your issue.


1

There are pros and cons for both options: A single master key for your Ansible account would reduce complexity but you would need to ensure the private key is very secure, even if the key were password protected you would want to ensure the key is encrypted at rest with a tool like BlackBox and backed up somewhere. System unique SSH keys would help with ...


1

I would look at AWS System Manager to do this instead of direct ssh. Create a SSM document to run the commands you want to run, then this can be invoked by an AWS cli command from your CI/CD pipeline. We do something the same to update configuration files from an s3 bucket, run as part of a Gitlab pipeline.


1

Do the following for each Vagrant machine you want Ansible to work with...in this example, using the machine master1: Do vagrant ssh-config > vagrant-ssh Enter content from vagrant-ssh into your ~/.ssh/config, modifying it as needed, like this example for some machine named master1: Host master1 HostName 127.0.0.1 User vagrant Port 2222 ...


1

Not sure if complete reinstall is a valid option for you, but for me this helped: sudo minikube delete After delete is finished, minikube start again


Only top voted, non community-wiki answers of a minimum length are eligible