Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

12 - Publishing outputs: Host key verification failed. #51

Closed
acca301 opened this issue Jul 4, 2016 · 8 comments
Closed

12 - Publishing outputs: Host key verification failed. #51

acca301 opened this issue Jul 4, 2016 · 8 comments

Comments

@acca301
Copy link

acca301 commented Jul 4, 2016

Walking through the tutorial step-by-step. Made a gist, added

 - name: resource-gist
   type: git
   source:
     uri: git@gist.github.com:71c94aad09a4adc12ebec5ac2794bab4.git
     branch: master

into 12_publishing_outputs/pipeline.yml. A build attempt fails in resource-gist with

Cloning into '/tmp/build/get'...
Host key verification failed.
fatal: Could not read from remote repository.

Note this is pull, we're not at the push stage yet.

The host key is certainly not in ~/.ssh/known_hosts inside the task container. How / where can I run ssh-keyscan or push `known_hosts' there?

@drnic
Copy link
Contributor

drnic commented Jul 4, 2016

AK, can I ask a favor? Can you please recreate this ticket with the concourse/git-resource project, link it to this issue and tag me as well (so I get notifications).
I'm sorry I'm not sure I know how to debug/ fix this issue myself.
Nic

On Tue, Jul 5, 2016 at 7:54 AM +1000, "Alexander Kuznetsov" notifications@github.com wrote:

Walking through the tutorial step-by-step. Made a gist, added

  • name: resource-gist
    type: git
    source:
    uri: git@gist.github.com:71c94aad09a4adc12ebec5ac2794bab4.git
    branch: master

into 12_publishing_outputs/pipeline.yml. A build attempt fails in resource-gist with

Cloning into '/tmp/build/get'...

Host key verification failed.

fatal: Could not read from remote repository.

Note this is pull, we're not at the push stage yet.

The host key is certainly not in ~/.ssh/known_hosts inside the task container. How / where can I run ssh-keyscan or push `known_hosts' there?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@acca301
Copy link
Author

acca301 commented Jul 5, 2016

Done.
BTW, your tutorial is great, unfortunately there are not many manuals made with such clarity.

@acca301
Copy link
Author

acca301 commented Jul 6, 2016

My bad. | was they key.
I usually do chomping with |-, thus I wrote it the way:

  resources:
  - name: foo
    type: git
    source:
      uri: ...
      private_key: |-
        ---BEGIN BLAH BLAH---
        .....
        ---END BLAH BLAH---

while the working syntax is

  resources:
  - name: foo
    type: git
    source:
      uri: ...
      private_key: |
        ---BEGIN BLAH BLAH---
        .....
        ---END BLAH BLAH---

@drnic
Copy link
Contributor

drnic commented Jul 6, 2016

Getting yaml right can be hard! Thanks for letting me know you found a solution. Thanks for nice comments about the tutorial.

On Wed, Jul 6, 2016 at 1:27 PM +1000, "Dr. Alexander Kuznetsov" notifications@github.com wrote:

My bad. | was they key.

I usually do chomping with |-, thus I wrote it the way:

resources:

  • name: foo
    type: git
    source:
    uri: ...
    private_key: |-
    ---BEGIN BLAH BLAH---
    .....
    ---END BLAH BLAH---

while the working syntax is

resources:

  • name: foo
    type: git
    source:
    uri: ...
    private_key: |
    ---BEGIN BLAH BLAH---
    .....
    ---END BLAH BLAH---


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@joshuajabbour
Copy link

If this |- typo was actually the problem (and I can't confirm it is; I'm also having auth issues but this hasn't fixed it for me), then you probably typed that because the readme says to use |-.

@joshuajabbour
Copy link

I don't think the problem is the |-. I can confirm both private_key: |- and private_key: | work, once I solved my underlying issue.

@jhunt
Copy link
Contributor

jhunt commented Nov 2, 2016

@joshuajabbour is your issue taken care of now?

@mkb
Copy link
Contributor

mkb commented Dec 8, 2016

Sounds like this has been addressed so I'm closing it out. @joshuajabbour if there's still an issue please let us know. Thanks!

@mkb mkb closed this as completed Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants