Allow writable root filesystem for flaresolverr
The image copies and patches the chromedriver binary to the hardcoded path /app/chromedriver at startup (no env override exists) and writes chromedriver caches under /app, so readOnlyRootFilesystem cannot hold; deviation documented in values.yaml. Reverts the HOME=/tmp workaround, which only covered the cache path, not the binary patching.
This commit is contained in:
2 files changed
+9
-10
No files matched your search
@@ -170,11 +170,6 @@ spec:
|
||||
env:
|
||||
- name: TZ
|
||||
value: {{ .Values.timezone | quote }}
|
||||
# flaresolverr writes chromedriver caches under $HOME (image
|
||||
# default /app, which is read-only); point HOME at the writable
|
||||
# /tmp emptyDir so the root filesystem can stay read-only.
|
||||
- name: HOME
|
||||
value: /tmp
|
||||
{{- include "freesailarr.env" (dict "root" $ "env" .Values.flaresolverr.env) | nindent 12 }}
|
||||
ports:
|
||||
- containerPort: 8191
|
||||
|
||||
Reference in new issue
Block a user