9
respostas

Erro ao tentar ansible-playbook -i /vagrant/configs/ansible

Boa noite,

Ao tentar executar o comando para inicialização do playbook recebo a mensagem de erro citada abaixo:

vagrant@ubuntu-bionic:~$ ansible-playbook -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml

fatal: [192.168.1.22]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: vagrant@192.168.1.22: Permission denied (publickey).", "unreachable": true}

O ping funciona:


vagrant@ubuntu-bionic:~$ ping 192.168.1.22 PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data. 64 bytes from 192.168.1.22: icmp_seq=1 ttl=64 time=0.653 ms --- 192.168.1.22 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9113ms rtt min/avg/max/mdev = 0.653/0.734/0.761/0.033 ms


As VMs estão rodando:


vagrant status Current machine states:

mysqldb running (virtualbox) phpweb running (virtualbox) mysqlserver running (virtualbox) ansible running (virtualbox)


Seguem os conteúdos dos arquivos:

Grato.

hosts:

########## [mysqlserver] 192.168.1.22

[mysqlserver:vars] ansible_user=vagrant ansible_ssh_private_key_file=/home/vagrant/id_bionic ansible_python_interpreter=/urs/bin/python3 ansible_ssh-commom_args='-o StrictHostKeyChecking=no'

playbook.yml:

##########

  • hosts: all handlers:

      - name: restart mysql
        service:
              name: mysql
              state: restarted
        become: yes

    tasks:

      - name: 'Instalar MySQL Server'
        apt:
              update_cache: yes
              cache_valid_time: 3600 #1 hora
              name: ["mysql-server-5.7", "python3-mysqldb"]
              state: latest
        become: yes
    
      - name: 'Criar usuario no MySQL'
        mysql_user:
              login_user: root
              name: phpuser
              password: pass
              priv: '*.*:ALL'
              host: '%'
              state: present
        become: yes
    
      - name: 'Copiar arquivo mysqld.cnf'
        copy:
              src: /vagrant/configs/mysqld.cnf
              dest: /etc/mysql/mysql.conf.d/mysqld.cnf
              owner: root
              group: root
              mode: 0644
        become: yes
        notify:
              - restart mysql

Vagrantfile:

##########

$script_mysql = <<-SCRIPT apt-get update && apt-get install -y mysql-server-5.7 && mysql -e "create user 'phpuser'@'%' identified by 'pass';" SCRIPT

Vagrant.configure("2") do |config|

config.vm.box = "ubuntu/bionic64"

  config.vm.define "mysqldb" do |mysql|        

    mysql.vm.network "public_network", ip: "192.168.1.24"
    mysql.vm.provision "shell", inline: "cat /configs/id_bionic.pub >> .ssh/authorized_keys"
    mysql.vm.provision "shell", inline: $script_mysql 
    mysql.vm.provision "shell", inline: "cat /configs/mysqld.cnf > /etc/mysql/mysql.conf.d/mysqld.cnf"
    mysql.vm.provision "shell", inline: "service mysql restart"
    mysql.vm.synced_folder "./configs", "/configs"
    mysql.vm.synced_folder ".", "/vagrant", disabled: true
end

config.vm.define "phpweb" do |phpweb|

    phpweb.vm.network "forwarded_port", guest: 8888, host:8888    
    phpweb.vm.network "public_network", ip: "192.168.1.25"

    phpweb.vm.provision "shell", inline: "apt-get update && apt-get install -y puppet"

        phpweb.vm.provision "puppet" do |puppet|
            puppet.manifests_path = "./configs/manifests"
            puppet.manifest_file = "phpweb.pp"
        end

end

    config.vm.define "mysqlserver" do |mysqlserver|
    mysqlserver.vm.network "public_network", ip: "192.168.1.22"

    mysqlserver.vm.provision "shell", inline: "cat /vagrant/configs/id_bionic.pub >> .ssh/authorized_keys"



end

    config.vm.define "ansible" do |ansible|
            ansible.vm.network "public_network", ip: "192.168.1.26"

        ansible.vm.provision "shell",
        inline: "cp /vagrant/id_bionic /home/vagrant && \
                chmod 600 /home/vagrant/id_bionic && \
        chown vagrant:vagrant /home/vagrant/id_bionic"

    ansible.vm.provision "shell",
                inline: "apt-get update && \
            apt-get install -y software-properties-common && \
            apt-add-repository --yes --update ppa:ansible/ansible && \
            apt-get install -y ansible"

end

end

9 respostas

Oi, Bruno, tudo bem?

Veja se essa aula te ajuda com esse erro: https://cursos.alura.com.br/course/infraestrutura-como-codigo-com-ansible/task/46792

Espero ter te ajudado!

Obrigado pela resposta, gerar a nova chave não resolveu, tentei também apagar o arquivo known_hosts sem sucesso, seguem comandos no terminal abaixo, grato:

/bionic$ ssh-keygen -t rsa

Generating public/private rsa key pair.

vagrant@ubuntu-bionic:~$ ls /vagrant/

Vagrantfile id_bionic src configs id_bionic.pub ubuntu-bionic-18.04-cloudimg-console.log

vagrant@ubuntu-bionic:~$ cp /vagrant/id_bionic.pub .

vagrant@ubuntu-bionic:~$ ls

id_bionic id_bionic.pub

vagrant@ubuntu-bionic:~$ cat id_bionic.pub

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHWWaZ7FN5alU0pxxu0knRy0LwRwl2MVFECGHkebdiktJfD0D57gKdNC36drbK479yPNjrXuKQiN6rkboShlkCxWBO9UZJQ6q6+NEmgh8A04KilR7HiFuUxx0pGq2jBunvVBFlDaYViUIKhKt20V8ssz1Va+dM8oDi0ddQqv4A8xx0xcFsHf7H3lDULlBgJP1kRvgOXxoqHfzzgG124So81BnNlYUyxIk1yOfL2ZVHYEJeMEK0uu8+7NFsYaqRyr05ikeBfchqD12nuaMlgKvELEuaD5mHdl53rfnTqpZdXkwKdl31RA1o+fKYpxaNxETntoB+lj0O4d89iIGYXuh9 05329594774@user-1562699

vagrant@ubuntu-bionic:~$ cat id_bionic.pub >> .ssh/authorized_keys

vagrant@ubuntu-bionic:~$ cat .ssh/authorized_keys

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDI28gvP4tq6cve8UIPqZzrii85W0ov9MqQX3FMs4YNYe0Py9thtgXz+/tv34uKa3qNXAfFK65AXdX7gbr+lHWtU3/b+ZY7z6PZ8p150DPOQpfm7xUdaw74qezplPFvyzhgooB2kW4qxoMzHDcmDSwm8kuvFG1nE+RvLUUHOgtUf6XwI0YQO81/HsP7LoLw2/PjlIlLAWywmdDSf/H1f0sbTaoPxx1TOivUudFe8p/5j6PyynReec+oAVpYZGzu0DprtqT+So4YShaM5zl6B9Zq+Pp7iSGp8G20w+ZXnKge8C8YLB1q1p8AJkHTDatIgM12IjcuT2Cwg0QwGiB+zQi1 vagrant ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHWWaZ7FN5alU0pxxu0knRy0LwRwl2MVFECGHkebdiktJfD0D57gKdNC36drbK479yPNjrXuKQiN6rkboShlkCxWBO9UZJQ6q6+NEmgh8A04KilR7HiFuUxx0pGq2jBunvVBFlDaYViUIKhKt20V8ssz1Va+dM8oDi0ddQqv4A8xx0xcFsHf7H3lDULlBgJP1kRvgOXxoqHfzzgG124So81BnNlYUyxIk1yOfL2ZVHYEJeMEK0uu8+7NFsYaqRyr05ikeBfchqD12nuaMlgKvELEuaD5mHdl53rfnTqpZdXkwKdl31RA1o+fKYpxaNxETntoB+lj0O4d89iIGYXuh9 05329594774@user-1562699 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHWWaZ7FN5alU0pxxu0knRy0LwRwl2MVFECGHkebdiktJfD0D57gKdNC36drbK479yPNjrXuKQiN6rkboShlkCxWBO9UZJQ6q6+NEmgh8A04KilR7HiFuUxx0pGq2jBunvVBFlDaYViUIKhKt20V8ssz1Va+dM8oDi0ddQqv4A8xx0xcFsHf7H3lDULlBgJP1kRvgOXxoqHfzzgG124So81BnNlYUyxIk1yOfL2ZVHYEJeMEK0uu8+7NFsYaqRyr05ikeBfchqD12nuaMlgKvELEuaD5mHdl53rfnTqpZdXkwKdl31RA1o+fKYpxaNxETntoB+lj0O4d89iIGYXuh9 05329594774@user-1562699

vagrant@ubuntu-bionic:~$ ansible-playbook -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml

PLAY [all] *

TASK [Gathering Facts] * fatal: [192.168.1.22]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: vagrant@192.168.1.22: Permission denied (publickey).", "unreachable": true}

PLAY RECAP * 192.168.1.22 : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0

vagrant@ubuntu-bionic:~$

Oi, Bruno, tudo bem?

Fazendo o mesmo código que você usou, que o do projeto da aula, eu obtive o mesmo erro, mas consertei com esse comando:

rm -r .vagrant.

Ela traz a pasta do projeto para o lugar certo. Depois disso, o , o código funcinou e as máquinas subiram. Testa e me fala se deu certo.

Obrigado pela resposta, infelizmente ainda não funcionou, duplicou as máquinas, que precisaram ser reconstruídas com o comando vagrant up, seguem os comandos no terminal, grato:

ambiente_dev/bionic$ cd .vagrant

ambiente_dev/bionic/.vagrant$ cd..

ambiente_dev/bionic$ rm -r .vagrant

ambiente_dev/bionic$ cd .vagrant

bash: cd: .vagrant: Arquivo ou diretório inexistente ambiente_dev/bionic$ vagrant ssh ansible

VM must be created before running this command. Run vagrant up first. ambiente_dev/bionic$ vagrant status

Current machine states:

mysqldb not created (virtualbox) phpweb not created (virtualbox) mysqlserver not created (virtualbox) ansible not created (virtualbox)

ambiente_dev/bionic$ vagrant destroy -f && vagrant up

######################### Primeiro ocorre o erro listado abaixo, e depois, ao submeter o comando novamente o erro muda e permanece o mesmo:

vagrant@ubuntu-bionic:~$ ansible-playbook -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml

PLAY [all] *

The authenticity of host '192.168.1.22 (192.168.1.22)' can't be established. ECDSA key fingerprint is SHA256:exuxbOlbguTFXZO/AkyfYhjMilkZ0TSgSrLIPNhju1Y. Are you sure you want to continue connecting (yes/no)? yes fatal: [192.168.1.22]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '192.168.1.22' (ECDSA) to the list of known hosts.\r\nvagrant@192.168.1.22: Permission denied (publickey).", "unreachable": true}

######################## Após submeter o comando do playbook a primeira vez e obter o erro citado acima, nas vezes seguintes em que submeto o comando, o erro abaixo é exibido:

vagrant@ubuntu-bionic:~$ ansible-playbook -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml

PLAY [all] *

fatal: [192.168.1.22]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: vagrant@192.168.1.22: Permission denied (publickey).", "unreachable": true}

Através do comando cat .ssh/authorized_keys, verifiquei a presença das seguintes chaves dentro das máquinas mysqlserver e ansible respectivamente:

vagrant@ubuntu-bionic:~$ cat .ssh/authorized_keys

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAatTgeCLqsxwULBP8hKgKKOi/r0mN/x4m8LGCRaw0OfoUkmgwndUhxg6OuiTnoJeXJz4ifqe3HHuseneFEq328AT70PG2O/0LHXdY759HSOOpKpAIxwsKDC4Ch7ujMGzYfa/yx6c/EKs77o/8VfNIYgARQP+eYWkk38vXSypaI4Ueyw1WJkb9tXd/+1zxSB4A5ouQ/XweaD1xUJEFAtCkGv/U6la4/GJwFn3iUx6RkzQFgxdJpD/dlyX2PVS8S1gglgWAre7DAC933WIpNP54CUmxy756XufmrWaBUf2OsOY4jm9V8hZzEwEXL7MJgeZLVMUU2170+ONEh3URBnbt vagrant ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCsMJCkDElZBKc9S2qtQ4QZHwflFOpeTRrcOv3kFF/6MFnbxjluDWvYyvG+E6hff2rCt6hxO/U7EJR69UC95z7oKhi7lFDJTvuHMSZwAI4tx+kJx+iL/D/MQwhjJz9J9S+DV1voExbMLNnAYr2iDidROOxs8owbeFFI4LKJeq0RsB0X+qCnptiO+YGDuvDPehH+qO/UcOrVcSXXFak6jUEwG0ei4AtzA4aAhyN6Vs2XzN6YKfbg1kqdBm3b+PAcr8rGUyTlXgEHdVSEzAA+VhjbDd74cAT/eGHpSHRZ0U76Zyfc5rKP+jQVNu9Ot08EYXBN7lln3uK2O92TmsiNaTqb haguenmcleod@haguenmcleod-Inspiron-5557

vagrant@ubuntu-bionic:~$ cat .ssh/authorized_keys ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDcyYJinnTlMOwrzeXyBYsqVHFNgbCh/kfcGbl9grJksl21sbM/B5Cbza0TiyaMCoETXfNJS+dKI0P6/jzqETz18Omrf4m+SAb67CKzwxwQoKLXheKoyuUhSIIV3eewpuUQrVTn/BmHvl4uQ3/8kGcFjygo05e2Yb19W4FWunxK6nIQAGft8u6OZtHlFN4yOrgncUBffoE4IVPP6H/Fajss1AxvbzNgSDW0wtvI3NGxQGsOtv/NCgmd38vDJn8O+l4h3IrksfQD6ZdZU/KNnedOG/Hym4+5NKuOeeX//5+i94WjTMa7VjkrWtEjX83+CL2sUTxl3MzKaIjKUx10lIIh vagrant ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCsMJCkDElZBKc9S2qtQ4QZHwflFOpeTRrcOv3kFF/6MFnbxjluDWvYyvG+E6hff2rCt6hxO/U7EJR69UC95z7oKhi7lFDJTvuHMSZwAI4tx+kJx+iL/D/MQwhjJz9J9S+DV1voExbMLNnAYr2iDidROOxs8owbeFFI4LKJeq0RsB0X+qCnptiO+YGDuvDPehH+qO/UcOrVcSXXFak6jUEwG0ei4AtzA4aAhyN6Vs2XzN6YKfbg1kqdBm3b+PAcr8rGUyTlXgEHdVSEzAA+VhjbDd74cAT/eGHpSHRZ0U76Zyfc5rKP+jQVNu9Ot08EYXBN7lln3uK2O92TmsiNaTqb haguenmcleod@haguenmcleod-Inspiron-5557

Boa noite, segue atualização, executando o comando para conexão do ansible ao playbook com o parâmetro -vvvv obtive a seguinte saída no terminal, grato:

vagrant@ubuntu-bionic:~$ ansible-playbook -vvvv -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml


fatal: [192.168.1.22]: UNREACHABLE! => { "changed": false, "msg": "Failed to connect to the host via ssh: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for \r\ndebug1: auto-mux: Trying existing master\r\ndebug1: Control socket "/home/vagrant/.ansible/cp/7d7f4ad4cf" does not exist\r\ndebug2: resolving "192.168.1.22" port 22\r\ndebug2: ssh_connect_direct: needpriv 0\r\ndebug1: Connecting to 192.168.1.22 [192.168.1.22] port 22.\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: fd 3 clearing O_NONBLOCK\r\ndebug1: Connection established.\r\ndebug3: timeout: 9992 ms remain after connect\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/vagrant/id_bionic type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/vagrant/id_bionic-cert type -1\r\ndebug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3\r\ndebug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3\r\ndebug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH compat 0x04000000\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: Authenticating to 192.168.1.22:22 as 'vagrant'\r\ndebug3: hostkeys_foreach: reading file "/home/vagrant/.ssh/known_hosts"\r\ndebug3: record_hostkey: found key type ECDSA in file /home/vagrant/.ssh/known_hosts:1\r\ndebug3: load_hostkeys: loaded 1 keys from 192.168.1.22\r\ndebug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521\r\ndebug3: send packet: type 20\r\ndebug1: SSH2_MSG_KEXINIT sent\r\ndebug3: receive packet: type 20\r\ndebug1: SSH2_MSG_KEXINIT received\r\ndebug2: local client KEXINIT proposal\r\ndebug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c\r\ndebug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa\r\ndebug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com\r\ndebug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com\r\ndebug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: compression ctos: zlib@openssh.com,zlib,none\r\ndebug2: compression stoc: zlib@openssh.com,zlib,none\r\ndebug2: languages ctos: \r\ndebug2: languages stoc: \r\ndebug2: first_kex_follows 0 \r\ndebug2: reserved 0 \r\ndebug2: peer server KEXINIT proposal\r\ndebug2: KEX algorithms

Boa noite, acho que o seu erro está em:

config.vm.define "mysqlserver" do |mysqlserver| mysqlserver.vm.network "public_network", ip: "192.168.1.22"

nessa linha -> mysqlserver.vm.provision "shell", inline: "cat /vagrant/configs/id_bionic.pub >> .ssh/authorized_keys"

Quando eu fiz o curso essa linha no meu script está diferente, está assim:

mysqlserver.vm.provision "shell", inline: "cat /vagrant/configs/id_rsa.pub"

Sem refazer a cópia de chave e etc, não vou lembrar totalmente, mas eu sei que funciona. Espero que ajude.

Obrigado pela resposta Leonardo Oliveira,

Acabei conseguindo resolver o problema, pelo menos de forma parcial, de fato o erro estava na chave pública, agora consigo fazer a conexão do ansible criando as chaves "depois" de as máquinas subirem. Com o Vagrantfile gerado nas aulas, que cita "/id_bionic.pub" e não "id_rsa.pub", e nenhum professor da Alura se interessou por esclarecer a dúvida completamente, as máquinas sobem porém o comando do playbook ainda apresenta erro, após subirem, os comandos abaixo geram uma chave nova, e permitem a conexão, o seu projeto conecta no ansible de primeira, sem precisar gerar as chave depois ? Grato.

Seguem os comandos:


-> vagrant ssh ansible
-> ssh-keygen -t rsa 
-> cd .ssh
-> cat id_rsa.pub -> copiar a chave publica
-> cd ..
-> exit
-> vagrant ssh mysqlserver
-> cd .ssh
-> vi authorized_keys -> colar a chave copiada
-> cd ..
-> exit
-> vagrant ssh ansible
-> ssh vagrant@192.168.1.22
-> exit
-> ansible-playbook -i /vagrant/configs/ansible/hosts /vagrant/configs/ansible/playbook.yml

E ai Bruno, tudo bom? Desculpa a demora, mas eu não recebi o e-mail avisando do comentário, então, o meu não tá funcionando, e como você mesmo comentou, essa chave de depois tem q ser adicionada no vagrant file pra fazer a conexão entre ansible e mysqlserver, sem senha, o que não existe no momento, eu não cheguei a fazer, e acho q durante esses dias vc pode ter resolvido, se resolveu me diz. Outra coisa, o nome da chave é sua escolha, por isso está bionic, escolha do professor, quando você faz automático, ela fica com rsa mesmo.

Obrigado pela resposta Leonardo, com o script que listei na minha última postagem consegui resolver o problema da conexão "depois" de as máquinas serem destruídas e recriadas, agora gostaria de já criar as VMs com as devidas chaves e conexão no momento da criação, com o script que postei abaixo consigo gerar a chave, entretanto esta ainda é recusada na hora da conexão, grato:

#OBS.: Crédito à consulta a postagem no StackOverflow, infelizmente não lembro o link:

$script_ansible_CHAVE_PUBLICA_LOCAL_COMUM = <<-SCRIPT
              yes | ssh-keygen -b 2048 -t rsa -f /home/vagrant/.ssh/id_rsa -q -N ""
            cp /home/vagrant/.ssh/id_rsa.pub /vagrant
              echo
              echo ********************************
              echo ********** id_rsa.pub **********
              echo ********************************
              echo
              cat /vagrant/configs/id_rsa.pub
              echo
        SCRIPT

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software