-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to change permissions inside a volumed folder on ReFS drive #13877
Comments
I need to clear this out too. I was only mounting my working directory so the host and the container would always be in sync. Today I found out that But still, the issue itself doesn't seem right, |
Having same issue. All files are on ReFS drive. Trying to start PostgreSQL inside docker compose gives this error message: chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted |
I'm running into the same issue. I've tried modifying the permissions of the directory both in Windows and in WSL but nothing seems to help. |
I'm having the same issue and can reproduce it with the steps provided from @PAXANDDOS as well. Is there any news on this? |
Also, not sure it's really related to microsoft/WSL#10792 - or did it fix the issue for you? |
Description
I'm using a ReFS drive for development purposes (so-called Dev Drive) and so far the only issue I'm having is with file/folder permissions. I was working on an NTFS drive before and haven't changed anything in the project since then. I have a whole working directory volumed like that:
But inside the container, every file and folder would have
root
ownership instead ofwww-data
(set in dockerfile). All my attempts to change that would literally do nothing. For example,chown -R www-data:www-data .
would take a while; after that, all files will remain withroot
ownership. That causes the application to fail trying to do something to the filesystem.Might be worth noting that I also have
Disk image location
(Docker Desktop -> Settings -> Resources) set to a folder on the same ReFS drive.Reproduce
docker compose up -d
docker compose exec test sh
root
instead ofwww-data
withls -la
chown
and see that nothing changesExpected behavior
Files and folder have
www-data
ownershipdocker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.7 API version: 1.43 Go version: go1.20.10 Git commit: afdd53b Built: Thu Oct 26 09:08:44 2023 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.26.1 (131620) Engine: Version: 24.0.7 API version: 1.43 (minimum version 1.12) Go version: go1.20.10 Git commit: 311b9ff Built: Thu Oct 26 09:08:02 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.25 GitCommit: d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f runc: Version: 1.1.10 GitCommit: v1.1.10-0-g18a0cb0 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
1F906053-8E46-4ABD-97BC-48F533E190A9/20240117164604
Additional Info
Windows 11 Pro 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250)
AMD Ryzen 7 5800X3D
32GB RAM
The text was updated successfully, but these errors were encountered: