SonarQube in docker containers without volume

We use a platform as a service to run web applications that do not support data persistence. I read the official SonarQube documentation that recommends using volumes to run in docker containers. How important is the use of volumes, and what do I lose without using volume?


Hi Bruno,

Welcome to the community!

There are 3 folders of the SonarQube server installation that should be persisted:

  • sonarqube/data keeps the ElasticSearch data such as the cache, index… this is a fundamental part for the functioning of SonarQube and you surely do not want to lose this data each time you recreate the SonarQube container as it could imply large boot times.
  • sonarqube/extensions keeps the SonarQube plugins that you have installed via the marketplace or other means. Probably not handy to have to re-install everything each time.
  • sonarqube/logs keeps the logs.

Not having the above folders persisted would pose many potential issues for a production level SonarQube instance in several scenarios and so, I strongly recommend you to look for a way to persist this.


1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.