You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eval "$(micromamba shell hook --shell=posix)" && micromamba activate base
{{ if .Values.diracx.pythonModulesToInstall }}
pip install{{ if .Values.developer.offline }} --no-build-isolation{{ end }} {{- range $moduleSpec := .Values.diracx.pythonModulesToInstall }} {{ $moduleSpec | quote }} {{- end }}
{{- end }}
{{ if .Values.developer.mountedPythonModulesToInstall }}
pip install{{ if .Values.developer.offline }} --no-build-isolation{{ end }} {{- range $moduleName := .Values.developer.mountedPythonModulesToInstall }} {{ if $.Values.developer.editableMountedPythonModules }}-e {{- end }}{{ $.Values.developer.sourcePath }}/{{ $moduleName }} {{- end }}
{{- end }}
{{- if and .Values.developer.enabled .Values.developer.enableCoverage }}
The helm chart generates it's own entrypoint for various reasons, however it still contains what the native docker image is supposed to have
For example:
diracx-charts/diracx/templates/diracx/diracx-container-entrypoint.yaml
Lines 11 to 32 in dad3fbc
https://github.com/DIRACGrid/container-images/blob/8f91a60b0da6e20196aecea087fe535e60d6a8d3/base/entrypoint.sh#L1-L66
However, when applying a change in the diracx-container entrypoint, we need to make sure to propagate it to the chart one, and this is cumbersome
(https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/)
The text was updated successfully, but these errors were encountered: