Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot run with read only root filesystem because /home/node/.cache directory cannot be created #65

Open
brokenjacobs opened this issue Jan 16, 2024 · 2 comments

Comments

@brokenjacobs
Copy link

When using read only root filesystem in the securityContext:

Error: ENOENT: no such file or directory, mkdir '/home/node/.cache'
2024-01-16T17:47:37.516Z | error    | Error: Exiting due to an error. "{ file: 'LoggerProxy.js', function: 'exports.error' }"
2024-01-16T17:47:37.517Z | error    | Error: ENOENT: no such file or directory, mkdir '/home/node/.cache' "{ file: 'LoggerProxy.js', function: 'exports.error' }"

And there is no extraVolumes/extraVolumeMounts in the values to propagate an emptyDir volume to this path to mitigate the issue.

@Vad1mo
Copy link
Member

Vad1mo commented Jan 16, 2024

Happy to accept and review PRs

@brokenjacobs
Copy link
Author

brokenjacobs commented Jan 17, 2024

I've reproduced this issue with Docker:
docker run -v .../n8n:/home/node/.n8n --read-only --platform linux/amd64 -it n8nio/n8n:1.22.3

Fails with this error.
docker run -v .../cache:/home/node/.cache -v .../n8n:/home/node/.n8n --read-only --platform linux/amd64 -it n8nio/n8n:1.22.3

Does not.

Interestingly enough the worker pods don't have this issue even though they are running read only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants