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

use new kaniko release #7012

Closed
1 of 2 tasks
gazal-k opened this issue Apr 4, 2020 · 0 comments · Fixed by #7013
Closed
1 of 2 tasks

use new kaniko release #7012

gazal-k opened this issue Apr 4, 2020 · 0 comments · Fixed by #7013

Comments

@gazal-k
Copy link

gazal-k commented Apr 4, 2020

Summary

Use newer release of kaniko

Steps to reproduce the behavior

Expected behavior

jx uses a newer version of kaniko. Some relevant fixes I'm specifically after:
GoogleContainerTools/kaniko#9
GoogleContainerTools/kaniko#826

Actual behavior

jx uses a gcr.io/kaniko-project/executor:debug-9912ccbf8d22bbafbf971124600fbb0b13b9cbd6 which is apparently close to gcr.io/kaniko-project/executor:debug-v0.10.0

Jx version

The output of jx version is:

jxl version

NAME               VERSION
jxl                0.0.158
Kubernetes cluster v1.14.9-eks-502bfb
kubectl            v1.17.3
helm client        3.1.2
git                2.25.1
Operating System   "Fedora release 31 (Thirty One)"

Jenkins type

  • Serverless Jenkins X Pipelines (Tekton + Lighthouse)
  • Classic Jenkins

Kubernetes cluster

EKS created using eksctl

Operating system / Environment

Fedora release 31 (Thirty One)

gazal-k added a commit to gazal-k/jx that referenced this issue Apr 4, 2020
fix jenkins-x#7012

Signed-off-by: Gazal K <mohamed.gazal@target.com.au>
jenkins-x-bot pushed a commit that referenced this issue Apr 5, 2020
fix #7012

Signed-off-by: Gazal K <mohamed.gazal@target.com.au>
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

Successfully merging a pull request may close this issue.

1 participant