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

Volume for plugins #99

Closed
DblK opened this issue Aug 4, 2017 · 1 comment
Closed

Volume for plugins #99

DblK opened this issue Aug 4, 2017 · 1 comment
Labels

Comments

@DblK
Copy link

DblK commented Aug 4, 2017

Could you add a volume to $SONARQUBE_HOME/extensions/plugins?
That way, we could install new plugins without having to build a new image based on that one.

Same goes for config folder

@Godin
Copy link
Member

Godin commented Aug 5, 2017

Quoting #75 (comment) :

We removed declaration of volume for directory extensions in 80366e3 for the very good reasons after discussion in docker-library/official-images#2437 (comment)

And AFAIK absence of explicit declaration of volume does not prevent externalization of this directory:

$ docker run -v /tmp/sonarqube/extensions:/opt/sonarqube/extensions sonarqube

or using docker-compose:

version: "2"

services:
  sonarqube:
    image: sonarqube
    volumes:
      - ./extensions:/opt/sonarqube/extensions

Same goes for config folder.

@Godin Godin closed this as completed Aug 5, 2017
@Godin Godin added the wontfix label Aug 5, 2017
@SonarSource SonarSource locked as resolved and limited conversation to collaborators Jan 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants