Add a notice/doc to warn about not puting a config.json at the root folder #7098
Closed
1 of 2 tasks
Labels
area/import
good first issue
Good for newcomers
kind/enhancement
An enhancement of an existing feature
priority/important-longterm
Summary
It took me a while to debug it but with the last jx versions you shouldn't have a config.json file at the root folder of your app, because if there is one, it will be used by kaniko to configure the docker registry, and depending on its content it will almost certainly cause a build error at the container-build step.
What put me on the right track after having commented all my overriden steps in my jenkins-x.yaml (with one of them copying a config.example.json to config.json): GoogleContainerTools/kaniko#887
A month ago it didn't cause any problem for this project, and my other projects don't have any problem at all.
Steps to reproduce the behavior
Have a config.json in the root folder of your app with anything but a kaniko config in it, like:
Expected behavior
A correct build.
Actual behavior
Build error at the step "container-build" in the "build" stage of the "release" pipeline:
Jx version
The output of
jx version
is:Jenkins type
Kubernetes cluster
AKS
The text was updated successfully, but these errors were encountered: