Enhancement description
I'd like to tell docker sandbox what env vars to use, and what file to take them from. It's really hard to work with sandboxes if I have to my env vars defined in my personal ~/.bashrc.
I want to do what I would do with docker run to set my env:
docker sandbox run -e X=Y ...
docker sandbox run --env-file /some/agent-only/env-vars ...
There's already patterns for managing env vars based around these. It's kind not intuitive that sandbox run commands don't follow suite.
Now as a workaround, I could make another user just to have some isolation between my environment (~/.bashrc) and my sandbox, but that's not convenient at all. I want to develop logged in as me, that's where all my other tools and bookmarks are - if I have to make a whole other user and switch context, it really gets in the way - especially on mac. I guess I could go CLI only, setup another user and some sudo scripts, but now I can't use the docker desktop UI anymore. So the workarounds aren't great.
Enhancement description
I'd like to tell docker sandbox what env vars to use, and what file to take them from. It's really hard to work with sandboxes if I have to my env vars defined in my personal ~/.bashrc.
I want to do what I would do with
docker runto set my env:docker sandbox run -e X=Y ...docker sandbox run --env-file /some/agent-only/env-vars ...There's already patterns for managing env vars based around these. It's kind not intuitive that
sandbox runcommands don't follow suite.Now as a workaround, I could make another user just to have some isolation between my environment (~/.bashrc) and my sandbox, but that's not convenient at all. I want to develop logged in as me, that's where all my other tools and bookmarks are - if I have to make a whole other user and switch context, it really gets in the way - especially on mac. I guess I could go CLI only, setup another user and some sudo scripts, but now I can't use the docker desktop UI anymore. So the workarounds aren't great.