Let's say I clone a git repo onto my NTFS drive. After that, I open that as a dev container in VS Code. Would +x permissions on shell scripts work then? In this scenario, the +x attribute is set on the file in git.
I know NTFS doesn't support it, and trying to understand what the workflow looks like.
My recommendation is that sadly it's just not worth it. NTFS not being case sensitive has caused me uncountable lost hours for why repos wouldn't compile. I don't understand people choosing to rely on case sensitivity for anything because it's a readability issue for me, but people do. The amount of times I've just re-cloned in the wsl drive and my weirdness goes away is too high
There has been some speculation that this will be really bad for Docker Desktop licensing. https://www.xda-developers.com/docker-on-windows-is-about-to...
Even apple jumps on it now with apple container.
It's time
Isn't Podman Desktop a decent alternative?
I hope this plays nice with regular WSL, and my non-standard networking configuration.
Nice! :)
Let's say I clone a git repo onto my NTFS drive. After that, I open that as a dev container in VS Code. Would +x permissions on shell scripts work then? In this scenario, the +x attribute is set on the file in git.
I know NTFS doesn't support it, and trying to understand what the workflow looks like.
My recommendation is that sadly it's just not worth it. NTFS not being case sensitive has caused me uncountable lost hours for why repos wouldn't compile. I don't understand people choosing to rely on case sensitivity for anything because it's a readability issue for me, but people do. The amount of times I've just re-cloned in the wsl drive and my weirdness goes away is too high
NTFS is case sensitive.
Ntfs supports alternative data streams so they probably use that to record the unix permission byres
[dead]