nestybox / nestybox/sysbox

S3 Server - EACCES permission denied

Open
#558 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
3.9k
Forks
230
Avg merge
7h 48m
Merged PRs (30d)
3

Description

os=ubuntu 20.04, kernel=5.18.2, docker=20.10.16, sysbox=0.5.2 EE, containerd=1.6.4, runc=1.1.1

docker run --runtime=sysbox-runc -d --restart always -p8000:8000 --name s3server scality/s3server

{"name":"DataFileStore","time":1654547614619,"error":{"errno":-13,"code":"EACCES","syscall":"access","path":"/usr/src/app/lib/../localData"},"level":"error","message":"Data path is not readable or writable","hostname":"7f910a099231","pid":148}
{"name":"S3","time":1654547614621,"error":{"errno":-13,"code":"EACCES","syscall":"access","path":"/usr/src/app/lib/../localData"},"level":"error","message":"Error initializing REST data server","hostname":"7f910a099231","pid":148}
fs.js:250
binding.access(pathModule._makeLong(path), mode);
^

Error: EACCES: permission denied, access '/usr/src/app/lib/../localMetadata'
at Error (native)
at Object.fs.accessSync (fs.js:250:11)
at MetadataFileServer.startServer (/usr/src/app/node_modules/arsenal/lib/storage/metadata/file/MetadataFileServer.js:124:12)
at Object. (/usr/src/app/mdserver.js:17:14)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:496:3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the supplied docker run command with --runtime=sysbox-runc and inspect the reported /usr/src/app/lib/../localData and localMetadata paths. Trace the EACCES failures through DataFileStore and MetadataFileServer.js. Done means the S3 server starts successfully and both data paths are readable and writable.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.