2 ms·

WSL container is now available for public preview

• craigaloewen 3mo ago
  Nice! :)
• mcraiha 3mo ago
  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-become-obsolete-and-wsl-containers-are-why/ https://www.xda-developers.com/docker-on-windows-is-about-to...
  • spacington 3mo ago
    Even apple jumps on it now with apple container. It's time
  • m-p-3 3mo ago
    Isn't Podman Desktop a decent alternative?
• tuwtuwtuwtuw 3mo ago
  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.
  • baby_souffle 3mo ago
    Ntfs supports alternative data streams so they probably use that to record the unix permission byres
  • Neywiny 3mo ago
    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
    • awson 3mo ago
      NTFS is case sensitive.
    • tuwtuwtuwtuw 3mo ago
      I'm cloning into WSL today. But I don't follow how that would work for these new WSL containers.
• axus 3mo ago
  I hope this plays nice with regular WSL, and my non-standard networking configuration.
• liquid153 3mo ago
  [dead]