DevOps Community Sponsored by Cloud Posse

SweetOps

Hey Everyone. Wondering if anyone here has gotten Geodesic working in Windows with WSL? I have it pretty close to working but AWS credentials aren't mounting properly. Error I'm seeing is "mkdir: cannot create directory ‘/localhost/.aws’: File exists"  I have Leapp working and can see the session in cli, but as soon as I jump into geodesic it doesn't carry in the creds.

Yes/no - all WSL support has been contributed

It has worked but if you are having trouble then something probably broke 

I'll give it a fresh build when I have time again this week.  Really strange it seems like you said, an issue with the mount.

It's my only major hang-up using atmos is that it has to be done on Mac/Linux.

The Geodesic launch script (<https://github.com/cloudposse/geodesic/blob/83919a061910f2d249cb698a5eea73dca2e5d1eb/rootfs/templates/wrapper#L140-L166|wrapper>) tries to find the right user `HOME` directory for WSL and mount it as `/localhost` . If that directory has a file (not a directory) named `.aws` in it, you will see this error. We expect (as does the AWS SDK and, by extension, Leapp) that `$HOME/.aws` is a directory and credentials and configuration files are stored in it.

My expectation is that the error is coming from <https://github.com/cloudposse/geodesic/blob/83919a061910f2d249cb698a5eea73dca2e5d1eb/rootfs/etc/profile.d/aws.sh#L12|this line> which I hope gives you enough information to figure out a workaround. I don't have access to a WSL system so I cannot be much more helpful than that. Please let us know if you find a solution.

have you guys seen an error related to dangling symlinks?

<@U01K0LQ6D52> Probably, but I'm not exactly sure what you mean. Please be more specific.

```✗ . [none] (HOST) localhost ⨠ ls -a
.       .aws           .bash_logout  .config    .landscape   .mozilla  .ssh                       .vscode-server  cert
..      .azure         .bashrc       .docker    .local       .pki      .sudo_as_admin_successful  Downloads       repo
.Leapp  .bash_history  .cache        .geodesic  .motd_shown  .profile  .viminfo                   aws             test.txt
 ⧉  xxxx
 ✗ . [none] (HOST) localhost ⨠ cd .aws
bash: cd: .aws: No such file or directory
 ⧉  xxxx
 ✗ . [none] (HOST) localhost ⨠ chmod 700 .aws
chmod: cannot operate on dangling symlink '.aws'```

We can see the directory .aws, but trying to cd into it returns no such file or directory.  Trying to change permissions return dangling symlink error.

You need to get things straight on your host machine. Your WSL `$HOME` directory has to have a `.aws/` subdirectory. That must be a real directory or a symlink relative to `$HOME` and below `$HOME` in the directory tree. If it points elsewhere, Geodesic won't be able to access it.

We ended up getting it to work, the problem was that the .aws directory was a symbolic link.  When we deleted the symlink and re-ran Leapp, it recreated the .aws directory local to my WSL instance and was seen by Geodesic.