You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploying splitter.groovy fails using IncrementalPackager
camel-k-kit-bm681ss85ojj9bdddrf0-builder builder {"level":"info","ts":1569489172.0693874,"logger":"camel-k.builder","msg":"step done in 0.004488 seconds","step":"github.com/apache/camel-k/pkg/builder/IncrementalPackager","phase":30,"kit":"kit-bm681ss85ojj9bdddrf0"}
camel-k-kit-bm681ss85ojj9bdddrf0-builder builder {"level":"info","ts":1569489172.069422,"logger":"camel-k.builder","msg":"executing step","step":"github.com/apache/camel-k/pkg/builder/kaniko/Publisher","phase":40,"kit":"kit-bm681ss85ojj9bdddrf0"}
camel-k-kit-bm681ss85ojj9bdddrf0-builder builder {"level":"info","ts":1569489172.0694778,"logger":"camel-k.builder","msg":"step failed with error: open /workspace/builder-713355563/package/context/Dockerfile: no such file or directory","step":"github.com/apache/camel-k/pkg/builder/kaniko/Publisher","phase":40,"kit":"kit-bm681ss85ojj9bdddrf0"}
I've tried switching to StandardPackager instead of IncrementalPackager and it seems to work. Any hint @astefanutti ?
The text was updated successfully, but these errors were encountered:
I've seen some "Invalid manifest" errors that I cannot replicate. Can be that, perhaps, the new minikube/kube version ships an improved docker registry with some metadata that is not interpreted by kaniko 0.9 and we have to upgrade it?
But I can't explain why the error is in the -builder pod and not in the Kaniko one (today...).
Context:
I've tried switching to StandardPackager instead of IncrementalPackager and it seems to work. Any hint @astefanutti ?
The text was updated successfully, but these errors were encountered: