#geodesic - December 2024

I finally got some time to explore WSL2 and I have a recommendation and a question for people using Geodesic under WSL2.

My recommendation is that you store your AWS credentials in your WSL2 filesystem ($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.

4.0.0-rc1
This is a release candidate for Geodesic v4. Please try it out and let us know what think in the #geodesic channel in the Cloud Posse Slack workspace. (Invitations available here.)
Read about the new features and breaking changes in the <a...

v3.4.1
🧰 Included Tools

Dependency updates @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2762150001" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/960" data-hovercard-type="pull_request"...

You are all invited to test out the Geodesic v4 release candidate. cloudposse/geodesic:4.0.0-rc2-debian. Some much-requested features and a bunch of cleanups. Still rough around the edges, but now is the time to find bugs and request changes. Read the draft release at https://github.com/cloudposse/geodesic/blob/v4/docs/ReleaseNotes-v4.md

Be sure to install the new wrapper (make all or make build + make install)!

4.0.0-rc1
This is a release candidate for Geodesic v4. Please try it out and let us know what think in the #geodesic channel in the Cloud Posse Slack workspace. (Invitations available here.)
Read about the new features and breaking changes in the <a...

4.0.0-rc2
This is a release candidate for Geodesic v4. Please try it out and let us know what think in the #geodesic channel in the Cloud Posse Slack workspace. (Invitations available here.)
Read about the new features and breaking changes in the <a...

4.0.0-rc2
This is a release candidate for Geodesic v4. Please try it out and let us know what think in the #geodesic channel in the Cloud Posse Slack workspace. (Invitations available here.)
Read about the new features and breaking changes in the <a...

v3.4.2
Prevent pre-release Docker images from being tagged as "latest".
Footnote
In every release, we update all unpinned packages to their latest packaged versions. These changes are not detailed here.

v3.4.2
Prevent pre-release Docker images from being tagged as "latest".
Footnote
In every release, we update all unpinned packages to their latest packaged versions. These changes are not detailed here.

The Geodesic version 4 release will have lots of new and updated documentation. Please review the drafts and leave comments here.
• Release Notes
• README
• Customization
• Environment Variables