-
Notifications
You must be signed in to change notification settings - Fork 90
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
Build Error: while running C:\NusskNacker\staging\nussknacker-staging\designer\runServer.sh #3954
Comments
Hi @pokkireddy, thanks for reporting an issue. Looks like your build is missing devModel ( If you build source using our scripts as described in Readme https://github.com/TouK/nussknacker/blob/staging/CONTRIBUTING.md#running-full-version-of-designer-from-command-line So in summary, the order of operations is as follows:
Please try to execute this instructions, and let us know if it had worked for you :) |
I have followed the same steps, still getting error. Please find the attached log. My use case is I want to change some UI text for ex: Instead of scenarios we would to like to change something else |
Based on the fix, I can able to runServer.sh without any error. My use case is I want to change some UI text for ex: Instead of scenarios we would to like to change something else |
Great :) This fix will problably be optimized a little bit before merge, but feel free to used it for now. Docker images are built with sbt native-packager plugin, so there is no dedicated Dockerfile in our codebase. The usage is straightforward:
Can you please also tell us more about your usecase for Nusskancker? And also whether you use Flink or Lite Engine for Nusskancker runtime? |
Could you please provide some steps like from which path to run the command "sbt dist/Docker/publishLocal". We have an existing k8s environment which we have to use Nussknacker with flink for datamapping and decision making. |
Scripts inside |
nussknacker-docker-image-update-notworking.docx Thanks for your prompt response and details. |
Also, please remember to pass flag |
I am getting some error while executing this command Please find the log file |
I have checked again, and on my local machine following steps produce successful dockerimage:
|
i have not modified anything and followed the above steps, still getting error. please find the |
looks like java version it is. I have run the build against java17 and got the same error as you do. Please use java11. |
I have installed java11 and tried build is success. I see the error (At the end) while generating docker image but i think this is not actual error. Please check the logs and confirm. |
On my local environment, logs look slightly different. But the last two lines of your logs indeed make an impression that the whole build is successful. Please confirm it on your own, that it's ok, by runing this docker image and seeing if everything is ok. |
I can able to run the docker image locally without any issue. |
You have probably imported this https://github.com/TouK/nussknacker-quickstart/blob/main/docker/streaming/scenarios/DetectLargeTransactions.json scenario to your Nussknacker which is meant for Flink engine. Please import that one https://github.com/TouK/nussknacker-quickstart/blob/main/k8s-helm/scenarios/DetectLargeTransactionsLite.json |
I have tried loading https://github.com/TouK/nussknacker-quickstart/blob/main/k8s-helm/scenarios/DetectLargeTransactionsLite.json it is working. |
It's not matter of docker image, but configuration. Additional tabs can be configured in your Helmchart using Alternatively you can use a lot more powerful approach, but a little bit more complicated. Provide secret or configMap with separate configuration file |
Build Error: while running C:\NusskNacker\staging\nussknacker-staging\designer\runServer.sh
Attached the log file for your reference. please let me know what is missed.
Environment (please fill in the following information):
-openjdk 17.0.6 2023-01-17
OpenJDK Runtime Environment Temurin-17.0.6+10 (build 17.0.6+10)
OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (build 17.0.6+10, mixed mode, sharing)
runServer.sh.log
The text was updated successfully, but these errors were encountered: