Let's break down how to fix this issue step by step—since you're new to Kubernetes, we'll start with the most critical diagnostic step first.

1. Get the Exact Error Details #

First, you need to uncover why Kubernetes is failing to create the Sonarqube container. Run this command, replacing <sonarqube-pod-name> with the actual Pod name from your kubectl get pods output:

kubectl describe pod <sonarqube-pod-name>

Scroll down to the Events section—this will spell out the root cause, like:

• A missing ConfigMap/Secret referenced in the volume mount
• A PersistentVolumeClaim (PVC) stuck in Pending state
• Incorrect file permissions on the mounted volume
• A typo in the container's mount path

2. Fix Common Volume Mount Issues (Tailored to This Helm Chart) #

Since you suspect the volume mount configuration, here are the most likely fixes for your Minikube setup:

Case 1: PVC Isn't Bound to a PersistentVolume #

Minikube has limited disk space, so if the Chart's default PVC size is too large, Kubernetes can't provision a matching PersistentVolume. Check your PVC status:

kubectl get pvc

If the status shows Pending, shrink the storage size via helm upgrade:

helm upgrade sonarqube devopskube/sonarqube --set persistence.size=5Gi

Minikube's default standard storage class handles smaller sizes like 5Gi without issues.

Case 2: Volume Permissions Don't Match the Sonarqube User #

Sonarqube runs as the sonarqube user (UID 1000) inside the container. If the mounted volume doesn't have read/write permissions for this user, Kubernetes can't start the container.

Fix this by adding security context settings to the Chart:

helm upgrade sonarqube devopskube/sonarqube --set securityContext.runAsUser=1000 --set securityContext.fsGroup=1000

This tells Kubernetes to adjust the volume's file permissions so the Sonarqube user can access it.

Case 3: Missing ConfigMap/Secret Resources #

If the deployment references a ConfigMap or Secret that the Helm Chart didn't create, you'll see an error like configmap "sonarqube-config" not found.

Check if these resources exist:

kubectl get configmaps
kubectl get secrets

If they're missing, re-run the Helm install with debug logs to see why resources failed to create:

helm install sonarqube devopskube/sonarqube --debug

3. Verify the Fix #

After making changes, check the Pod status again:

kubectl get pods

If the Sonarqube Pod transitions to Running, you can access it via minikube service sonarqube to confirm it's working correctly.

内容的提问来源于stack exchange，提问作者Always_Beginner