You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to ask your opinion about using Apple's container framework (https://github.com/apple/container) as an alternative sandbox runtime for ralphex on macOS 26.
container runs OCI images in lightweight Apple VMs and exposes a Docker-like CLI (container run, -v, --rm, etc.), so in many cases it can stand in for docker run without much rework. For agent workflows this is attractive because each run gets its own VM-level isolation while still feeling like a normal container invocation.
I'm wondering whether ralphex could support container as a drop-in adapter alongside Docker, or whether that is effectively already possible today. Do you have a sense of how much effort would be involved — is it mostly a matter of swapping the docker binary, or are there assumptions in ralphex (image building, networking, exec, mounts) that would need a dedicated adapter?
Here's the kind of invocation I have in mind, just to illustrate:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I wanted to ask your opinion about using Apple's
containerframework (https://github.com/apple/container) as an alternative sandbox runtime for ralphex on macOS 26.containerruns OCI images in lightweight Apple VMs and exposes a Docker-like CLI (container run,-v,--rm, etc.), so in many cases it can stand in fordocker runwithout much rework. For agent workflows this is attractive because each run gets its own VM-level isolation while still feeling like a normal container invocation.I'm wondering whether ralphex could support
containeras a drop-in adapter alongside Docker, or whether that is effectively already possible today. Do you have a sense of how much effort would be involved — is it mostly a matter of swapping thedockerbinary, or are there assumptions in ralphex (image building, networking, exec, mounts) that would need a dedicated adapter?Here's the kind of invocation I have in mind, just to illustrate:
container run \ -v "$PWD:/workspace/" \ -v "$HOME/.claude-creds.json:/home/node/.claude/.credentials.json" \ --rm -it $DOCKER_IMAGE \ sh -c "claude --model haiku -p $PROMPT < /dev/null"All reactions