After update to 1.6.0 container no longer starts

[FRvanderVeen]

I'm attempting to update my drydock container to 1.6.0 from 1.5.2. But the container won't start. In the console (via portainer) I see:

[21:29:42.570] INFO (drydock/7): drydock is starting
[21:29:42.576] INFO (drydock/7): Load store from (/store/dd.json) {"component":"store"}

node:fs:2111
  binding.chmod(path, mode);
          ^
Error: EPERM: operation not permitted, chmod '/store'
    at Object.chmodSync (node:fs:2111:11)
    at enforceStorePermissions (file:///home/node/app/dist/store/index.js:42:8)
    at Module.init (file:///home/node/app/dist/store/index.js:166:5)
    at file:///home/node/app/dist/index.js:41:17 {

  errno: -1,
  code: 'EPERM',
  syscall: 'chmod',
  path: '/store'
}

Node.js v24.19.0

Not sure whether it's a bug or some configuration issue.

When I attach the console to the running (1.5.2) container I can do chmod without issues.

[scttbnsn]

Thanks for the clean stack trace, that made this easy to pin down. It's a 1.6.0 regression: startup now tries to chmod the store directory as a hardening step, and on mounts where chmod isn't allowed (NFS/CIFS volumes, non-root setups) it crashes instead of continuing. 1.5.2 didn't do this, which is why the update broke it.

Two options right now: make the container's user the owner of the /store mount (then the chmod succeeds), or hold on 1.5.2 briefly. The real fix, chmod failure becomes a warning instead of a crash, lands in v1.7.0-rc.4 and will be backported to the 1.6.1 line.