That's why I went with a different strategy and scope: Copy the current Git repo into a sandboxes dir, mount that copy in the container. The tradeoff is disk space allocated per sandbox, but I'm OK with that.
Just a little bit, I want coding agents to work their own disposable copy of a git repo. Here is a quick rundown of what it does:
It copies the current Git repo into the sandboxes dir, mounts that copy at /workspace in the container. The original repo is never mounted writable, so I don't care if the agent goes to town/wild in there (peace of mind).
It also builds cached Debian/mise/Elixir/Phoenix images, can start a private Postgres container, publishes selected localhost ports, reuses dependency/build caches, and prints commands on exit for reviewing diffs, exporting patches, applying them back to the real repo, or reopening the same sandbox later. Pi, and OpenCode are configured with proper LLM access keys (derived from my own).
So spinning a new sandbox is a matter of cding into a project directory and run something like: `ai-sandbox --port 4000 --postgres somedbname` or `ai-sandbox --port 4001` if I don't need DB support. Then when running the server in the container I can access it from the host machine to review in my browser.
The real solution to these kind of problems is sandboxing. I use podman through a bash script to launch a container whenever I want an agent to work on one of my repos. When done I just generate git patches and port back everything generated.
In this way I'm not afraid of letting the agents totally lose on my computer.
I have a new Ryzen 7 CPU (you know, 8 cores, 16 threads), with 64GB RAM and for HDD a Samsung 960 PRO M.2 drive.
But when I went and plugged in an external Seagate 4TB drive, and tried to "dd zero" the s#it out of it, my whole system became unresponsive after a while, obviously I had to reset the machine as it wouldn't "kill -9" the process that made the system unresponsive.
Trying to type was a no go as keys would sometimes become "stuck". Moving the mouse around was an exercise in predictability too.
All this happened in the latest Ubuntu 17.04 64bit... #sadstory
How did you realize that your master was a living Enlightened Being? can you give the specific questions and answers that you used to recognize him as such?
How can you know what Enlightenment is very correctly? does that mean that you are yourself Enlightened? If so, that would explain how can you sanction everyone else's Enlightenment, like all of Zen monks, etc.
Also, how do you know that indeed a Buddha comes every 3000 years? where is the Truth pointing to that?
Fullstack Engineer
PELT stack: Phoenix, Elixir, LiveView and Tailwind CSS. Can do some Vue.js too ;)
Empathic, honorable, humble, smart, honest, thoughtful, with a knack for travel & seeing new places.
===============================
Zen hunting.
===============================
In case you want to look at a CV: https://lobotuerto.com/about/cv
---
meet.hn/city/20.8052225,-99.8837376/Querétaro