onlyotdn commented on issue #2849:
URL: 
https://github.com/apache/incubator-streampark/issues/2849#issuecomment-1632744851

   @A-little-bit-of-data 
   1. After you have built the image (by executing ./build.sh), if you 
encounter an error message stating that the /opt/streampark_workspace directory 
is missing during runtime, you can create it and add the necessary access 
permissions. Then, test it locally first to ensure it works correctly 
(accessing http://localhost:10000/). You should be able to log in and see the 
project interface. This step is to verify if the compiled image has any issues.
   
   2. Temporarily modify the Java startup parameters in the 
streampark-console/streampark-console-service/src/main/assembly/bin/streampark.sh
 file. The "&" at the end is used to start the program in the background. 
Remove the "&" to delete it.
   ```
     eval $NOHUP $_RUNJAVA $JAVA_OPTS \
       -classpath "$APP_CLASSPATH" \
       -Dapp.home="${APP_HOME}" \
       -Dlogging.config="${APP_CONF}/logback-spring.xml" \
       -Dspring.config.location="${PROPER}" \
       -Djava.io.tmpdir="$APP_TMPDIR" \
       $APP_MAIN >> "$APP_OUT" 2>&1 "&"
   ```
   3. Recompile the project. Just like we tested locally, it requires the 
/opt/streampark_workspace directory. Add the following line to the Dockerfile: 
"RUN mkdir -p /opt/streampark_workspace". Then use the Dockerfile to build your 
image. After that, update the image in your Helm chart. Now you can 
successfully start it.
   <img width="1268" alt="image" 
src="https://github.com/apache/incubator-streampark/assets/138647779/d939e5f7-ab3d-4455-bb24-27af7dc13c8d";>
   <img width="1500" alt="image" 
src="https://github.com/apache/incubator-streampark/assets/138647779/c957fa55-9bf5-4623-a625-218279a57c55";>
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to