linux/arm64 Docker build fails with "No space left on device" during chown #1966
Description
While working on updating Dockerfiles to Node.js 24, I noticed that the linux/arm64 Docker build for the server-api release is failing due to a disk space exhaustion during a recursive ownership change.
The failure happens at the following step:
RUN chown -R asyncapi:nodejs /app
Error observed:
No space left on device
This appears to be related to GitHub Actions runner disk limitations (especially on linux/arm64), as the recursive chown traverses a large node_modules tree produced during the build. The issue does not seem to be a functional problem with the Node 24 upgrade itself.
Relevant CI run:
https://github.com/asyncapi/cli/actions/runs/20818339702/job/59799766497
Proposed approach
One possible way to mitigate this could be to reduce the scope of the recursive chown operation (for example, limiting it to runtime-required directories instead of the entire /app tree), or to adjust the build steps to avoid unnecessary ownership changes on large dependency directories.
I did not include any changes related to this in the Node 24 Dockerfile update PR in order to keep its scope focused, but I’m happy to help investigate further or propose a fix if this direction makes sense.