Volume enabled causes EACCES error.
bluebonnetlane
PROOP

2 months ago

Volume mounted at /data throws EACCES permission denied on mkdir. n8n running as node user, volume owned by root. Actually anytime I have Volume enabled I get an EACCES error.

Closed$10 Bounty

3 Replies

Status changed to Open Railway about 2 months ago


Status changed to Awaiting Railway Response Railway about 2 months ago


bluebonnetlane
PROOP

2 months ago

Thank you. Mount path and user folder are /data. I've tried both chown settings - each causes a crash. chown: /data Operation not permitted. The deploy crashed.


domehane
FREE

2 months ago

Hello bluebonnetlane,

the reason chown keeps failing is that railway overwrites any permission changes when it mounts the volume, so chown never actually works , that's why you get "operation not permitted"

the fix is to create a custom dockerfile with just this added at the end:

USER root

then point your railway service to that dockerfile. root already owns the mount so n8n will start without any permission issues

Hope this help you :)


bluebonnetlane
PROOP

2 months ago

Thank you very much. The fix I'm going to deploy is to move to DigitalOcean. All my workflows were lost and I've spent the day trying to implement Volume with no success. Time to cut bait. Thanks again.


Status changed to Closed brody about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...