-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[bitnami/sonarqube] Extensions doesn't get copied to application extension folder when the jvmOpts include a javaagent setting #55271
Comments
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
What would be the best way to handle the chicken and egg problem of the timing and the way the volumes and paths are handled from the install and the sonarqube container . A possible solution would be to run the mount and copy (persist) two times, not ideal. The original sonarqube chart copys the plugin directly to the application/extension folder, so i think the real solution would need some deeper changes in the way how the container handle the volumes and mounts. Any thoughts what would be the best way to solve the issue with javaagents not available on starting th eapp first time? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
hi @codedreality, Could you try using
|
No it exits with same error. I although tried setting with extraProperties but since the string contains |
Let me create an internal task for the team to take a deeper look at the issue and create a fix. We will reach you back here as soon as our workload allow us. |
@aoterolorenzo Found this project https://github.com/adrianmusante/docker-sonarqube that install the plugin on top of the bitnami sonarqube version. |
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
Maybe @adrianmusante can contribute here? |
Name and Version
bitnami/sonarqube:10.3.0
What architecture are you using?
amd64
What steps will reproduce the bug?
Using
bitnami/sonarqube chart
version: 4.3.0
and configure it to install additional extensions, ex. the community branch plugin with theprovisioning folder
SONAR_CE_JAVAADDITIONALOPTS
to"-javaagent:/opt/bitnami/sonarqube/extensions/plugins/sonarqube-community-branch-plugin-1.18.0.jar=ce"
andSONARQUBE_WEB_JAVA_ADD_OPTS
to"-javaagent:/opt/bitnami/sonarqube/extensions/plugins/sonarqube-community-branch-plugin-1.18.0.jar=web"
.What is the expected behavior?
The container should start without an error.
What do you see instead?
Sonarqube exits with error 1 in the app initializing phase:
The InitContainer already downloaded the plugin and stored it in the
provisioning
-folderAdditional information
The file
rootfs/opt/bitnamo/scripts/libsonarqube.sh
defines functionsonarqube_initialize
which starts sonarqube to initialize the database if not already done.The call to
sonarqube_start_bg
fails with the exit code 1 due to the fact that the jvmOpts are already set with the javaagent which is still not copied to the extension folder.Afterwards persisting of the sonarqube installation and the copy from the
$SONARQUBE_MOUNTED_PROVISIONING_DIR
should run to copy the extension to the right folder, but this point is not reached due to the error above.The text was updated successfully, but these errors were encountered: