I also had this problem because I work with several computers, so despite the fact that I downloaded both ssh public keys into the digital ocean before creating a drop, when I went in, I could do it on both machines, if I logged in as root,
however, when I first pressed the button
$ git remote add dokku dokku@my.server.url $ git push dokku
as is happening in the digital oceanic manual i.
I found out that the user 'dokku' had only one of the keys loaded into his authorized key file.
so here is what i did. In my terminal, I used $ cat ~/.ssh/id_rsa.pub , which will display your public ssh key, and I highlighted it all and copied it.
I logged into my server as the root $ ssh root@my.server.url , then made my path to the dokku $ cd /home/dokku/.ssh/ user authorized keys folder
Then I discover that $ nano authorized_keys now in this file I already had one key, but you may not have one. In any case, I inserted my ssh key into this file and left the file.
From there, I was very good, if I clicked using the dokku user, it does not ask for a password, because it already recognizes my ssh key. By the way, there is a way to simplify all this, as two steps, but sometimes I like to do it a long way to make sure that the key really got into the file.
mkrinblk
source share