Clever Geek Handbook

Configuring ssh runner for gitlab ssh denied

I am trying to set up a simple gitlab CI for an angular project

I just made a staging runner.

Here is an excerpt from config.toml in / etc / gitlab -runner

  name = "awsTest10"
  url = "http://gitlab.XXXXXXX/ci"
  token = "XXXXXXXXXXXXXXXXXXXXX"
  executor = "ssh"
  [runners.ssh]
    user = "root"
    host = "ec2-XX-XX-XX-XX.eu-west-1.compute.amazonaws.com"
    port = "22"
    identity_file = "/root/.ssh/id_rsa"
  [runners.cache]

I created an ssh key with root and I copied the public part to gitlab expands the keys. I've done ssh-add before.

When I use the runner, I get the following output:

Running with gitlab-ci-multi-runner 1.11.1 (a67a225)
  on awsTest10 (e1ce142d)
Using SSH executor...
ERROR: Preparation failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Will be retried in 3s ...
Using SSH executor...
ERROR: Preparation failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Will be retried in 3s ...
Using SSH executor...
ERROR: Preparation failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Will be retried in 3s ...
ERROR: Job failed (system failure): ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

thanks for the help

+3


source to share


1 answer


I had the same problem. I have attached the public key to ~/.ssh/authorized_keys

and uncommented the line AuthorizedKeysFile %h/.ssh/authorized_keys

in the file /etc/ssh/sshd_config

. Then I restarted the ssh service and it works for me.



+1


source






More articles:


All Articles