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

EACCES Error: permission denied #206

Closed
Fred-DTV opened this issue Dec 30, 2024 · 2 comments
Closed

EACCES Error: permission denied #206

Fred-DTV opened this issue Dec 30, 2024 · 2 comments

Comments

@Fred-DTV
Copy link

Fred-DTV commented Dec 30, 2024

Everything seems to be working fine but the uploads stop at about a third of the process and I receive this error:

Timestamp=1735581676487000000 Logger=FirefoxSend Type=uncaughtException Severity=0 Pid=1 EnvVersion=2.0 Fields={"error":"Error: EACCES: permission denied, unlink '/uploads/14-5ad94595f26438cd'","stack":"\n at Object.unlinkSync (node:fs:1718:3)\n at WriteStream.<anonymous> (/app/server/storage/fs.js:34:12)\n at WriteStream.emit (node:events:402:35)\n at WriteStream.emit (node:domain:475:12)\n at emitErrorNT (node:internal/streams/destroy:157:8)\n at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)"}

It's running vie docker-compose and Portainer on my Synology NAS

I thought it might be a volume issue but I've tried mounting it directly in the compose and via NFS and neither is working.

Anyone has ideas what is causing this?

My docker-compose:

services:
  send:
    image: '${DOCKER_SEND_IMAGE}'
    restart: always
    ports:
      - '1234:1234'
    labels:
      tsdproxy.enable: "true"
      tsdproxy.name: "transfer"
      tsdproxy.funnel: "true"
    volumes:
      - /volume1/Archiv/TRANSFER:/uploads
    env_file:
      - stack.env

  redis:
    image: 'redis:alpine'
    restart: always
    volumes:
      - send-redis:/data

volumes:
  uploads:
    driver: local
    driver_opts:
      type: nfs
      o: addr=2.39.2.50,rw,nolock,soft,nfsvers=4.1
      device: :/volume1/Archiv/TRANSFER
  send-redis:
  proxy-certs:
  proxy-vhost:
  proxy-html:

And the envs:
Screenshot 2024-12-30 at 19 08 17

@timvisee
Copy link
Owner

timvisee commented Feb 4, 2025

Are you sure the volume mounts are set up correctly?

This error usually comes up if the container itself does not have access to it. What happens if you allow any user to write to that directory?

@Fred-DTV
Copy link
Author

Fred-DTV commented Feb 6, 2025

Oh i feel so stupid now.... Obviously it was the NFS folder which didn't have the right permissions...
I was looking at the mounts and user mappings for ages but never at the actual folder 😅

Thanks for your help!

@Fred-DTV Fred-DTV closed this as completed Feb 6, 2025
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