⚠️ Please verify that this bug has NOT been reported before.
🛡️ Security Policy
Description
I have noticed that when /root/.docker is mounted as read-only for giving access to credentials, Dockge tries to write to /root/.docker/buildx when saving a stack. The entire saving of the stack then fails.
This did not happen for me on the latest Dockge version by louislam.
👟 Reproduction steps
- Mount /root/.docker:/root/.docker:ro
- Run Dockge as root
- Try to save an existing stack (even without changes) in Dockge
👀 Expected behavior
It should first check if the folder is mounted as read-write and only then write to it
😓 Actual Behavior
It tries to write to /root/.docker in any case.
Dockge Version
1.2
💻 Operating System and Arch
Synology DSM 7.2.2-72806
🌐 Browser
Safari
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
}
stderr: 'mkdir /root/.docker/buildx: read-only file system\n'
stdout: '',
signal: null,
code: 1,
at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
at maybeClose (node:internal/child_process:1101:16)
at ChildProcess.emit (node:events:519:28)
at ChildProcess.done (/app/node_modules/promisify-child-process/index.cjs:70:19)
2025-11-10T19:55:03+01:00 [VALIDATE] WARN: Error: Process exited with code 1
}
🛡️ Security Policy
Description
I have noticed that when /root/.docker is mounted as read-only for giving access to credentials, Dockge tries to write to /root/.docker/buildx when saving a stack. The entire saving of the stack then fails.
This did not happen for me on the latest Dockge version by louislam.
👟 Reproduction steps
👀 Expected behavior
It should first check if the folder is mounted as read-write and only then write to it
😓 Actual Behavior
It tries to write to /root/.docker in any case.
Dockge Version
1.2
💻 Operating System and Arch
Synology DSM 7.2.2-72806
🌐 Browser
Safari
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output