Hello #CB84E9V54 👋 - 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