-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: run goose in a docker-style sandbox #44
Conversation
Co-authored-by: Adrian Cole <[email protected]>
&& pipx ensurepath | ||
|
||
# Install goose-ai CLI using pipx | ||
RUN pipx install goose-ai |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the image was built before and this layer is cached, the user won't have the latest goose-ai
if there is a new release.
We could either to disable the cache of this layer or the user can install the latest in the docker container
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lifeizhou-ap what about if this instead was built as part of the py release workflow - and pushed as a versioned image to the GH docker registry - would that be suitable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! We'll revisit publishing these in the future
* origin/main: docs: add in ollama (block#82) chore: add just command for releasing goose (block#55) feat: support markdown plans (block#79) feat: add version options (block#74) docs: fixing exchange url to public version (block#67) docs: Update CONTRIBUTING.md (block#69) chore: create mkdocs for goose (block#70) docs: fix broken link (block#71) feat: give commands the ability to execute logic (block#63) feat: jira toolkit (block#59) feat: run goose in a docker-style sandbox (block#44)
Co-authored-by: Adrian Cole <[email protected]>
This change allows goose to run inside a docker container for those you are more interested in just trying it out without it running entirely in their environment.
To build it:
docker build -t goose . docker run -it --env OPENAI_API_KEY goose
This will open a new goose session that uses OPENAI (can do similar with anthropic etc) in an environment you can let it play in (it can clone things, try to build etc) all in a container.
If interested, can have this automatically published to make it easier for people to tyre kick