-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
docker-compose up fails with "can't find gid for group sonarqube: no such group: sonarqube" #958
Labels
bug
Something isn't working
Comments
I'm unable to replicate this (MacOs Arm, Docker 25), but the issue does make sense given the group was removed in SonarSource/docker-sonarqube@8e556d6. I'll drop the assignment of the group in the |
mc1arke
added a commit
that referenced
this issue
Sep 7, 2024
The sonarqube images no longer create a sonarqube group for the sonarqube user to be placed into, instead they put the sonarqube user in the root group. To prevent the plugin builds failing when attempting to set the plugin ownership to a group that doesn't exist, the `chown` command is being altered to only set the user ownership, not the associated group.
mc1arke
added a commit
that referenced
this issue
Sep 7, 2024
The sonarqube images no longer create a sonarqube group for the sonarqube user to be placed into, instead they put the sonarqube user in the root group. To prevent the plugin builds failing when attempting to set the plugin ownership to a group that doesn't exist, the `chown` command is being altered to only set the user ownership, not the associated group.
... and I've realised my change is wrong: the chmod should be |
mc1arke
added a commit
that referenced
this issue
Nov 16, 2024
Not all the Sonarqube image variants contain a group named sonarqube, so the `chown` command fails as it's unable to find the target group. To overcome this the group is being set to `0` which should always exist as the root user's group.
mc1arke
added a commit
that referenced
this issue
Nov 17, 2024
Not all the Sonarqube image variants contain a group named sonarqube, so the `chown` command fails as it's unable to find the target group. To overcome this the group is being set to `0` which should always exist as the root user's group.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Step 7/11 : COPY --from=builder --chown=sonarqube /home/build/project/build/libs/sonarqube-community-branch-plugin-*.jar /opt/sonarqube/extensions/plugins/
unable to convert uid/gid chown string to host mapping: can't find gid for group sonarqube: no such group: sonarqube
To Reproduce
Steps to reproduce the behavior:
Step 7/11 : COPY --from=builder --chown=sonarqube /home/build/project/build/libs/sonarqube-community-branch-plugin-*.jar /opt/sonarqube/extensions/plugins/
unable to convert uid/gid chown string to host mapping: can't find gid for group sonarqube: no such group: sonarqube
Expected behavior
SonarQube Community Edition running with plugin.
Screenshots
Logs:
Software Versions
SONARQUBE_VERSION=10.6-community
PLUGIN_VERSION=1.22.0-SNAPSHOT
Additional context
Linux 6.5.0-1025-azure #26~22.04.1-Ubuntu SMP Thu Jul 11 22:33:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: