Launch an autonomous AI agent with sandboxed execution in 2 lines of code
11–20 of 26 posts
Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#12[flagged]
Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#13I was curious, so I dug a bit. Under the hood it's effectively running: docker run --rm -w $PWD:/workspace \ python:3.11-slim \ pip install -q patchpal && \ Which cool, great, I sure love "pip install"ing every time instead of just baking a single container image with it already installed. This isn't any sort of fancy or interesting sandboxing, this is shelling out to "docker run", and not even using docker as well a…
That doesn’t sound right - the LLM told them it was a fantastic idea!
Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#14I was curious, so I dug a bit. Under the hood it's effectively running: docker run --rm -w $PWD:/workspace \ python:3.11-slim \ pip install -q patchpal && \ Which cool, great, I sure love "pip install"ing every time instead of just baking a single container image with it already installed. This isn't any sort of fancy or interesting sandboxing, this is shelling out to "docker run", and not even using docker as well a…
> Which cool, great, I sure love "pip install"ing every time instead of just baking a single container image with it already installed. Obviously the correct thing for such a use case would be building their own image with whatever tools are needed and then using that. Unfortunately, then they’d probably get roasted for not maintaining the image well enough and not having proper enough automation set up to keep it re…
Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#15Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#16Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#17Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#18Re: Launch an autonomous AI agent with sandboxed execution in 2 lines of code
#19Earlier quoted context omitted.
> Which cool, great, I sure love "pip install"ing every time instead of just baking a single container image with it already installed. Obviously the correct thing for such a use case would be building their own image with whatever tools are needed and then using that. Unfortunately, then they’d probably get roasted for not maintaining the image well enough and not having proper enough automation set up to keep it re…
You just set up CI/CD on GitHub and have it dump an image into ghcr it’s trivial. Claude excells at seeing up workflows. I don't know why anyone bothers with Dockerhub at all really.
Probably because Docker Hub has great discoverability. For my own needs I use Gitea Packages and Woodpecker CI cause GitHub actions feels worse (also in comparison to GitLab CI) or maybe sometimes Nexus as a registry when I need to decouple from my Git platform or need a pull through proxy no matter the original source (I also build my own base and language runtime images but just host upstream PostgreSQL for example). I also use Claude quite heavily but the reality is that not everyone does and anything that we say should “just” be done often won’t because of a variety of reasons (limited free time also being one of those).
All of that is a bit like saying "I don't know why anyone would willingly inflict Docker upon themselves when Podman exists!" or maybe that people should just prefer FreeBSD jails or NixOS. I will say, however, that making the good stuff easier to do is always a good move.