fix: initContainer execution with skipChown enabled (#43)

- fix initContainer execution with skipChown enabled
- adjusted main container to always skip chown (will be done by initContainer)
- adjusted ci to disable skipChown (like it was before due to the wrong check)

charts/owncloud/templates/deployment.yaml

@@ -41,7 +41,7 @@ spec:
               mountPath: {{ .Values.owncloud.volume.root }}
           resources:
             {{- toYaml .Values.initResources | nindent 12 }}
-        {{- if not .Values.skipChown }}
+        {{- if not .Values.owncloud.skipChown }}
         - name: "init-{{ .Chart.Name }}-chown"
           image: {{ template "owncloud.image" . }}
           command: ['sh', '-c', "chown -R www-data:www-data {{ .Values.owncloud.volume.root }}"]
@@ -378,7 +378,7 @@ spec:
             - name: OWNCLOUD_SKIP_CHMOD
               value: {{ .Values.owncloud.skipChmod | quote }}
             - name: OWNCLOUD_SKIP_CHOWN
-              value: {{ .Values.owncloud.skipChown | quote }}
+              value: "true"
             - name: OWNCLOUD_SMB_LOGGING_ENABLE
               value: {{ .Values.owncloud.smbLoggingEnable | quote }}
             - name: OWNCLOUD_SQLITE_JOURNAL_MODE

ci/ci-values.yaml

@@ -6,6 +6,9 @@ service:
   type: NodePort
   port: 8080
 
+owncloud:
+  skipChown: false
+
 initResources:
   limits:
     cpu: 100m