There are already some in built tools and technologies, but configuring them is little complex. Setting up a persistent Docker volume: a working example. As multiple Docker container images are getting created day-by-day, monitoring them is very important.

persistentVolumeClaim: claimName:sonar-data-claim. It's worth noting that you can only use persistent storage with the EC2 launch type, not with Fargate. First of all, we need to pull both the official Docker images for Sonarqube and Postgres. The docker image being used to create this resource is image: sonarqube; You can change the number of pods by updating replicas: 1; Label app: sonar-deployment has to match the selector defined in the service; Persistent volume claim created above is used for storage i.e.

That's why in this article we will only be considering the EC2 launch type. You can remove unused volumes using docker volume prune.

This template deploys Sonarqube in an Azure App Service web app Linux container using the official Sonarqube image and backed by an Azure SQL Server. A given volume can be mounted into multiple containers simultaneously. You can follow along with this example, where we'll: create an ECS Cluster built on top of 2 EC2 instances. As Docker usage and adoption is growing faster and faster, monitoring Docker container images is becoming more challenging.

Additionally, we need the ubuntu image as this image will be used to create a volume container. My Sonar-Dockerfile: FROM sonarqube:lts-alpine My sonar-startscript: #!/bin/bash image=sonarqube-test container=test-sonar docker stop ${container} docker rm ${container} docker rmi ${image} docker build ... How to bind mounted persistent volumes problem on docker ? When no running container is using a volume, the volume is still available to Docker and is not removed automatically. docker pull sonarqube docker pull postgres docker pull ubuntu. When you mount a volume, it may be named or anonymous. This Azure Resource Manager (ARM) template was created by a member of the community and not by Microsoft.