#geodesic - January 2022

Hello #geodesic 👋 - Love the work! New to Geodesic, not new to IaC, so forgive my n00b questions that have probably been asked and answered many times.

First, is there a recipe for the BindFS issue that may not be fully baked, but I could leverage for myself? I've working through the process of adding a user with the correct gid:uid and am having issues with the environment (e.g. bash: kube_ps1: command not found at every prompt) and am thinking that that route may be an anti-pattern, and that the BindFS solution could offer a more conformant, and simple path forward. But I don't know. Which brings me to the second question: what is the best way to adapt Geodesic so it won't step on my local permissions?

I've built several iterations of containerized tool delivery systems, and am dying to feel comfortable using Geodesic. But I have to know when and where a process is writing into my home directory without the correct bits, and Geodesic set off several alarms when I fired it up. I run Arch Linux and use Zsh as my default shell, if that makes a difference.

Anyway, I'm going to continue learning the tools on the assumption that I'll figure permission bits later, hopefully with your help 🙏 😄

Here's my Dockerfile:

# syntax=docker/dockerfile:1

FROM cloudposse/geodesic:latest-debian

ENV PROMPT_STYLE="unicode"

RUN apt-get update -y && \
  groupadd -g 1234 rbellamy && \
  useradd -d /conf -G sudo -g rbellamy -u 1234 rbellamy && \
  sed -i 's/sudo[[:space:]]ALL=(ALL:ALL) ALL/sudo ALL=(ALL) NOPASSWD: ALL/' /etc/sudoers

USER rbellamy

For issue 594, @Mike Crowe has a potential fix

@Mike Crowe would you be willing to share?

I will, might need a few more days to get it polished

Hey All 👋

Atmos arrived in my inbox (great newsletter BTW) and it looks great but the readme looks like it's not up to date. Is there somewhere else I can read through?

Checking out geodesic and running into a curious situation and not sure if someone else has already encountered it before and got a fix. My workstation is running Windows 10 Pro so I run Ubuntu 20.04 LTS under WSL2. I was impressed my ssh agent forwarding worked (Yubikey on Win 10 through to Linux WSL passed to geodesic); however the AWS config isn't making it through. $HOME/.aws under WSL is actually a symlink back to the Windows user home directory and is where Leapp is putting the credentials so under geodesic that mount point doesn't exist

Am I missing it or does the latest default geodesic image not include atmos? I see the tutorial image added it in it's Dockerfile. If that's the case then I assume I just need to generate my own custom image.

Hi there, hope this isn’t too simple, but I just started with Geodesic v0.149.1-debian
on macOS Catalina (Intel processor), and
when I bring up a geodesic container using the installed command, geodesic,
my home folder is not mounted to /localhost and I don’t see any erros
I have gogoled and don’t see a relevant solution yet, do you have any advice what to try?
Thank you ver ymuch

Has anyone done any testing with Geodesic and the new stable release of rancher desktop rather than docker? I plan to give it a try in the next couple days, just curious if anyone has tried already and has any feedback.

Open question: When you install geodesic (or maybe even when you run geodesic in a folder), that folder is typically your project folder. I'm working on a PR that improves usability, and I want the launch folder to be something we can reference inside geodesic somehow. I've though of 2 options:
• Map the current folder into a fixed path such as /project (my favorite so far). usage: cd /project to return to your code (if you changed out of that folder for some reason)
• Continue the workdir setup and set an environment variable GEODESIC_WORKDIR pointing to this folder. usage: cd $GEODESIC_WORKDIR
Does anybody else see the value of this, or is there something I'm missing in standard usage? I haven't needed it a lot, but after a couple of times of:

cd ~/.ssh
(do something)
cd /localhost/Programming/terraform/system/project

I sure would like to reference /project instead

I think we already implemented this

See our recent Prs

@Erik Osterman (Cloud Posse) @Jeremy (UnderGrid Network Services) -- Just submitted quite a few geodesic PR's to improve it (and spark discussion). LMK any thoughts you have

@Yonatan Koren has joined the channel

Any geodesic users who ssh and use ssh-agent? I believe the current /etc/profile.d/ssh-agent.sh is a bit rough, and doesn't really work as expected (but I'd like confirmation that others see the issue too).

In Linux, upon startup it finds an agent (I see * Found SSH agent config), but then it starts a new agent (I'm not sure how /var/tmp/.ssh-agent is getting created before /etc/profile.d/ssh-agent.sh runs).

The proper way to test if the agent is alive is:

  ssh-add -l &>/dev/null
  if [[ $? -gt 1 ]]; then ...

Based on my experience with ssh-agent, I think a better implementation is here, which should work well in mac as well as linux worlds. With this setup, I can:

ssh-add ~/.ssh/id_rsa
geodesic
(in geodesic shell)
ssh-add -L 

and see my SSH keys from the host.

Can somebody with a mac build with this /etc/profile.d/ssh-agent.sh and confirm that it works for Mac users as well?