Fix adguardhome PVC mount shadowing the binary

Mounting the whole PVC at /opt/adguardhome hid the AdGuardHome binary
that ships inside the image at that exact path, crash-looping the pod
(exec: /opt/adguardhome/AdGuardHome: no such file or directory). Use
subPath mounts for work/ and conf/ instead, same as the original split
hostPath layout, just backed by one PVC now.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01566weDFku8TaRC2CJUPVM1
This commit is contained in:
sha
2026-08-24 02:49:12 +03:00
co-authored by Claude Sonnet 5
parent cc5ecd25ce
commit 8d7e017109
2 changed files with 9 additions and 2 deletions
+1 -1
View File
@@ -2,7 +2,7 @@ apiVersion: v2
name: adguardhome name: adguardhome
description: AdGuard Home DNS server Helm chart description: AdGuard Home DNS server Helm chart
type: application type: application
version: 0.1.7 version: 0.1.8
appVersion: "0.107.79" appVersion: "0.107.79"
annotations: annotations:
version-source: github-release:AdguardTeam/AdGuardHome version-source: github-release:AdguardTeam/AdGuardHome
+8 -1
View File
@@ -46,8 +46,15 @@ spec:
resources: resources:
{{- toYaml .Values.resources | nindent 12 }} {{- toYaml .Values.resources | nindent 12 }}
volumeMounts: volumeMounts:
# subPath mounts, not the whole /opt/adguardhome -- the AdGuardHome
# binary itself ships inside the image at /opt/adguardhome/AdGuardHome,
# so mounting the entire parent directory shadows it.
- name: data - name: data
mountPath: /opt/adguardhome mountPath: /opt/adguardhome/work
subPath: work
- name: data
mountPath: /opt/adguardhome/conf
subPath: conf
volumes: volumes:
- name: data - name: data
persistentVolumeClaim: persistentVolumeClaim: