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

Error creating integration context with buildStrategy: routine on minikube #665

Closed
lburgazzoli opened this issue May 19, 2019 · 2 comments
Closed
Labels
area/build-operator Related to the internal image build operator

Comments

@lburgazzoli
Copy link
Contributor

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"}

/cc @astefanutti

@astefanutti
Copy link
Member

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.

@lburgazzoli
Copy link
Contributor Author

Relates to #681

@astefanutti astefanutti added the area/build-operator Related to the internal image build operator label Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-operator Related to the internal image build operator
Projects
None yet
Development

No branches or pull requests

2 participants