Jeremy G (Cloud Posse)
12/17/2024, 5:48 AM$HOME/.aws) and then you make a symbolic link to it in your Windows home directory (%USERPROFILE%\.aws). In PowerShell with admin privileges, and WSL2 using the Ubuntu distro, the command looks like this:
New-Item -ItemType SymbolicLink -Path "$env:USERPROFILE\.aws" -Target "\\wsl$\Ubuntu\home\<Ubuntu-user-name>\.aws"
The reason to do it this way is that Geodesic (or any Docker container) is going to have a hard time following a symbolic link from the WSL filesystem to the Windows filesystem, but a Windows program run by the user should easily follow the symbolic link into the WSL filesystem. (A different Windows user on the same computer may not be able to reach into the WSL filesystem of the first user, but in this case, that is a good thing, giving further protection to the secrets.)
Now, my question: How do you install Docker Desktop in WSL2 to avoid the issue of files having the wrong ownership permissions. I don't recall how I installed it, but I'm having this problem, and we long ago determined that on Linux, this was an issue of installing Docker as a daemon and not in "rootless" mode. But we have an accommodation for this in Geodesic (--geodesic-host-bindfs-enabled), and I'm finding myself having to use that. My reading of the Docker Desktop documentation is that this is overall easier and better than trying to run Docker in "rootless" mode with WSL2, but I would love to be wrong about that.loren
12/17/2024, 2:03 PMJeremy G (Cloud Posse)
12/17/2024, 7:45 PMloren
12/17/2024, 8:23 PMloren
12/17/2024, 8:24 PMJeremy G (Cloud Posse)
12/17/2024, 8:47 PMloren
12/17/2024, 9:51 PMJeremy G (Cloud Posse)
12/17/2024, 9:53 PMloren
12/17/2024, 9:59 PM