Repository navigation
Linux permissions are ignored when running write operation #58326
Description
Version
24.0.1
Platform
x86_64
Subsystem
No response
What steps will reproduce the bug?
Run an image build like so with the attached files
docker build . --progress=plain --no-cache
How often does it reproduce? Is there a required condition?
There is no condition. It manifests itself on every run.
What is the expected behavior? Why is that the expected behavior?
Writing on a readonly file should fail.
What do you see instead?
Here's a file with the output I'm getting.
Additional information
- Other images I have tested node on (with precompiled binaries): ubuntu:24.04, public.ecr.aws/amazonlinux/amazonlinux:2023
- Docker Version: 25.0.8, build 0bab007
- this bug causes the following 2 tests to fail:
Activity
bnoordhuis commentedon May 14, 2025
Does it happen outside docker? Docker does some funky overlayfs stuff and doesn't always do it right.
bnoordhuis commentedon May 17, 2025
No follow-up and as it's almost certainly a docker bug (not the first time it's been reported) I'm going to go ahead and close this.
Stefan9283 commentedon May 19, 2025
Hi! Yes, it seems to be an issue with Docker specifically. I tested it on bare metal and the tests are now behaving as expected. Thank you
test: disable chmod tests failing in Docker
chore: bump node to v22.16.0 (main) (#47217)
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
chore: bump node to v22.16.0 (36-x-y) (#47214)
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
test: disable chmod tests failing in Docker
chore: bump node to v22.16.0 (35-x-y) (#47213)
chore: bump node to v22.16.0 (main) (electron#47217)