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

%nuclio: error: cannot deploy #74

Open
felihong opened this issue Feb 21, 2020 · 2 comments
Open

%nuclio: error: cannot deploy #74

felihong opened this issue Feb 21, 2020 · 2 comments

Comments

@felihong
Copy link

felihong commented Feb 21, 2020

Hi there,

following https://www.kubeflow.org/docs/components/misc/nuclio/ I deployed Nuclio in my GKE cluster, the following errors are triggered when testing with the nlp example in my kubeflow notebook:

%nuclio deploy -d <dashboard-external-ip> -n nlp -p default 


[14:08:55.311] (I) Deploying function 
[14:08:55.311] (I) Building 
[14:08:55.381] (I) Staging files and preparing base images 
[14:08:55.382] (I) Building processor image [imageName: "nuclio/processor-nlp:latest"]
[14:09:10.728] (W) Create function failed, setting function status [errorStack: "
Error - exit status 1
    .../nuclio/nuclio/pkg/cmdrunner/cmdrunner.go:131

Call stack:
stdout:
The push refers to repository [localhost:5000/nuclio/processor-nlp]

stderr:
Get http://localhost:5000/v2/: dial tcp [::1]:5000: connect: connection refused

    .../nuclio/nuclio/pkg/cmdrunner/cmdrunner.go:131
Failed to push image
    .../nuclio/nuclio/pkg/dockerclient/shell.go:157
Failed to push docker image into registry
    .../pkg/containerimagebuilderpusher/docker.go:55
Failed to build processor image
    .../nuclio/nuclio/pkg/processor/build/builder.go:242
"]

Moreover deployment a function to the above dashboard with cli nuctl works well, any ideas where should I start to address this issue? Thanks.

@chathurawidanage
Copy link

I am having the same issue.

@yaronha
Copy link
Contributor

yaronha commented Apr 20, 2020

@chathurawidanage seems like a nuclio registry config issue, @pavius @liranbg any ideas why it would fail?

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

3 participants