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

reuse of a PVC in writeonce, problem of env variable N8N_RELEASE_DATE #158

Open
vaboston opened this issue Mar 4, 2025 · 2 comments
Open

Comments

@vaboston
Copy link

vaboston commented Mar 4, 2025

Hello,
You are using the same PVC name for two deployments (basic and webhook), is it normal ?
volumes: - name: "data" {{ include "n8n.pvc" . }}
For me, you can't reuse a PVC already attach with ReadWriteOnce accessMode.

Secondly, I can’t run the n8n Docker container with webhook arguments; I encounter this error: Invalid timestamp value for N8N_RELEASE_DATE: $(date -u +"%Y-%m-%dT%H:%M:%SZ")
When I run my Docker container with the -e flag and a valid release date, the container exits with code 1 without any logs (even in debug mode). Could this be because the HOSTNAME and URL environment variables are not set?

Thanks

@Vad1mo
Copy link
Member

Vad1mo commented Mar 5, 2025

there should be different PVCs, I'll correct that... in the next release

@Fank
Copy link
Collaborator

Fank commented Mar 7, 2025

@vaboston the issue with the N8N_RELEASE_DATE has already been reported and fixed by n8n: n8n-io/n8n#13661

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

3 participants