jx: Create Spring Error: running skaffold steps

When I run the command “jx create spring”, pipeline stopped at pushing image to docker-registry:

...
Successfully built a904e0f4574a
Successfully tagged 4b1be5fc883375942973dbacf2e0d4b9:latest
Digest: 4b1be5fc883375942973dbacf2e0d4b9:latest
Successfully tagged 172.21.133.137:5000/jenkinsx/demo84:0.0.1
The push refers to a repository [172.21.133.137:5000/jenkinsx/demo84]
Error: running skaffold steps: build: build step: running push: Get https://172.21.133.137:5000/v2/: http: server gave HTTP response to HTTPS client
Usage:
  skaffold run [flags]

Flags:
  -f, --filename string       Filename or URL to the pipeline file (default "skaffold.yaml")
  -h, --help                  help for run
  -p, --profile stringArray   Activate profiles by name
  -t, --tag string            The optional custom tag to use for images which overrides the current Tagger configuration
      --toot                  Emit a terminal beep after the deploy is complete

Global Flags:
  -v, --verbosity string   Log level (debug, info, warn, error, fatal, panic (default "warning")

[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Promote to Environments)
Stage 'Promote to Environments' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] cleanWs
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
[Pipeline] input
Pipeline failed. 
We will keep the build pod around to help you diagnose any failures.

I entered the jenkins-x-docker-registry pod, it shows on shell: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:262: starting container process caused "exec: \"bash\": executable file not found in $PATH"

sh-3.2# jx version
NAME           VERSION
jx             1.1.55
Jenkins X      0.0.678
Kubernetes     v1.8.8-2+9d6e0610086578
Helm Client    v2.8.1+g6af75a8
Helm Server    v2.8.1+g6af75a8
Kubectl Client v1.7.4
Git            git version 2.6.4

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 34 (11 by maintainers)

Most upvoted comments

I’ve added this to the FAQ along with workarounds as folks hit this fairly frequently: https://jenkins-x.io/faq/issues/#http-server-gave-http-response-to-https-client

jstrachan on Jul 11, 2018

As @spennec, I’m experiencing this problem on Azure Kubernetes Services (AKS). I’m not to keen on doing manual changes on the worker nodes as it would make it more problematic when physically scaling the cluster.

@jstrachan, you mentioned a workaround by using an external docker registry. Can you give some details on how to do that? Which places needs to be changed; where do I add the authentication credentials for the registry; and other details you think might be of importance.

bremnes on May 13, 2018

@ysaakpr Your issue is the same as mine. You have to set the insecure-registries on ALL the NODES. I created a file /etc/docker/daemon.json with the contents: { "insecure-registries": [ "xxx.xxx.xxx.xxx:5000" ] } where xxx.xxx.xxx.xxx is the ip address shown for the docker-registry SERVICE. This ip will not change unless you redeploy the service! You need to reboot the nodes. I tried just restarting docker but that failed miserably!

CobraFlow on May 11, 2018