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
Installed camel-k on a brand new installation of minikube v1.0.1 with the following add-ons installed:
addon-manager: enabled
dashboard: enabled
default-storageclass: enabled
ingress: enabled
registry: enabled
storage-provisioner: enabled
When running an integration, the related context fails to be created because of:
"error":"stat /workspace: no such file or directory"
Full stack-trace:
{"level":"error","ts":1558282189.3706098,"logger":"camel-k","msg":"Unexpected error while creating a temporary dir","error":"stat /workspace: no such file or directory","stacktrace":"github.com/apache/camel-k/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/apache/camel-k/pkg/util/log.Logger.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:70\ngithub.com/apache/camel-k/pkg/util/log.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:191\ngithub.com/apache/camel-k/pkg/builder.(*defaultBuilder).Build\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/builder/builder.go:66\ngithub.com/apache/camel-k/pkg/controller/build.(*scheduleRoutineAction).build\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/controller/build/schedule_routine.go:107"}
The routine build strategy is currently not supported with the kaniko publish strategy. The main reason is to support different installation paths, like OLM, in addition to kamel CLI, that prevent creating resources like PVCs before hand.
I plan to work on a service build strategy that would off-load the build controller in a separate service and decorate the routine build strategy.
In the meantime, we may want to improve the error handling, and fail fast when the --build-strategy option is set to routine for Kubernetes / Kaniko.
Installed camel-k on a brand new installation of minikube v1.0.1 with the following add-ons installed:
When running an integration, the related context fails to be created because of:
Full stack-trace:
/cc @astefanutti
The text was updated successfully, but these errors were encountered: