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

failed to get previous image: connect to repo store #18

Open
jromero opened this issue Feb 26, 2021 · 0 comments
Open

failed to get previous image: connect to repo store #18

jromero opened this issue Feb 26, 2021 · 0 comments
Labels
status/incomplete Issue or PR that doesn't have enough information provided. type/bug Issue that reports an unexpected behaviour.

Comments

@jromero
Copy link
Member

jromero commented Feb 26, 2021

Cloned from tektoncd/catalog#591

Expected Behavior

I'm following the example for a buildpack build here: https://github.com/tektoncd/catalog/tree/master/task/buildpacks/0.2/tests
I'm getting the following error:

�[31;1mERROR: �[0mfailed to get previous image: connect to repo store 'https://github.com/cloudfoundry-samples/cf-sample-app-spring': Get "https://https/v2/": dial tcp: lookup https on 172.30.0.10:53: no such host

I'm probably doing something wrong but this error does help explaining what. My code can be found here (it's basically the same thing as the example:
https://github.com/raffaelespazzoli/openshift-enablement-exam/tree/master/misc4.0/tekton/buildpackpipeline

Actual Behavior

the error described above.

Steps to Reproduce the Problem

https://github.com/raffaelespazzoli/openshift-enablement-exam/tree/master/misc4.0/tekton/buildpackpipeline

run this pipeline with the defaults.

Additional Info

@jromero jromero added status/incomplete Issue or PR that doesn't have enough information provided. type/bug Issue that reports an unexpected behaviour. labels Feb 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/incomplete Issue or PR that doesn't have enough information provided. type/bug Issue that reports an unexpected behaviour.
Projects
None yet
Development

No branches or pull requests

1 participant