search

concourse / pool-resource

atomically manages the state of the world (e.g. external environments)
Apache License 2.0
54 stars 36 forks source link

Failed to authenticate with private_key #57

Closed schmurfy closed 2 years ago

schmurfy commented 3 years ago

I setup a resource with a private_key but all i get when I push is:

acquiring lock on: builds
waiting for lock

failed to broadcast the change to lock state!
err: exit status 128
git-err: ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I have done some digging trying to figure out the issue, what I tried was replacing /opt/go/out $1 >&3 < $payload in /opt/resource/out by:

ssh -v git@github.com

And it works fine with the key added to the ssh agent.

I also did another test after the first failure which worked too:

git -C /tmp/pool-resource619427837 fetch origin locks

The issue seems to only arise when the go app is the one executing git.

schmurfy commented 3 years ago

is there anybody using private_key without this issue ?