Created
June 4, 2021 05:07
-
-
Save tannisroot/590f8af37be88ada4f5c8a3280e3235d to your computer and use it in GitHub Desktop.
vagranfile
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ubuntu1804: Enter file in which to save the key (/home/vagrant/.ssh/id_rsa): | |
ubuntu1804: /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/vagrant/.ssh/id_rsa.pub" | |
ubuntu1804: /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed | |
ubuntu1804: | |
ubuntu1804: /usr/bin/ssh-copy-id: ERROR: ssh: connect to host 10.118.190.221 port 22: Connection refused | |
ubuntu1804: /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/vagrant/.ssh/id_rsa.pub" | |
ubuntu1804: /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed | |
ubuntu1804: | |
ubuntu1804: /usr/bin/ssh-copy-id: ERROR: ssh: connect to host 10.118.190.41 port 22: Connection refused | |
Pushing lutris-buildbot/3-buildbot32-sshsetup.sh to /home/ubuntu/3-buildbot32-sshsetup.sh: 100% (911.11MB/s) | |
ubuntu1804: chown: cannot access '/home/ubuntu/.ssh/config': No such file or directory | |
ubuntu1804: Enter file in which to save the key (/home/ubuntu/.ssh/id_rsa): | |
ubuntu1804: ./3-buildbot32-sshsetup.sh: line 5: sshpass: command not found | |
Pushing lutris-buildbot/4-buildbot64-sshsetup.sh to /home/ubuntu/4-buildbot64-sshsetup.sh: 100% (529.03MB/s) | |
ubuntu1804: chown: cannot access '/home/ubuntu/.ssh/config': No such file or directory | |
ubuntu1804: Enter file in which to save the key (/home/ubuntu/.ssh/id_rsa): | |
ubuntu1804: ./4-buildbot64-sshsetup.sh: line 5: sshpass: command not found | |
The SSH command responded with a non-zero exit status. Vagrant | |
assumes that this means the command failed. The output for this command | |
should be in the log above. Please read the output to determine what | |
went wrong. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment