#I’m trying to use `goose` with container
1 messages · Page 1 of 1 (latest)
Making a thread for it, here's my goose config:
extensions:
developer:
bundled: true
display_name: Developer
enabled: true
name: developer
timeout: 300
type: builtin
container-use:
name: container-use
type: stdio
enabled: true
cmd: cu
args:
- stdio
envs: {}
GOOSE_MODEL: gemini-2.5-pro-preview-06-05
GOOSE_PROVIDER: google
Maybe I'm missing something, does it work if you run just goose or do you need to do goose run -t "blah" in a non-interactive mode? @rancid tide
testing right away 👀
sorry got sidetracked -- testing now 🙏
Finally got the gemini payment config set ; i was on the free plan until now but it turns out i was rate limited ahah 👼
Ok I'm digging a bit -- seems to work rn for me ; Do you have a container runtime already ?
can you please do docker ps and check if the dagger engine is appearing ?
To answer your question, both are working. What I currently see with your config:
( O)> what tools do you see
Of course! I have a variety of tools available, organized into extensions. Here's a look at what I can do:
### container-use
This extension allows me to work with containerized development environments.
* **environment_open**: Create or open a development environment from a git repository.
* **environment_update**: Update an environment with new instructions, tools, or configurations.
* **environment_run_cmd**: Run a command inside the environment.
* **environment_file_list**: List files in a directory within the environment.
* **environment_file_read**: Read the contents of a file within the environment.
* **environment_file_write**: Write or overwrite a file within the environment.
* **environment_file_delete**: Delete a file within the environment.
* **environment_add_service**: Add a service (like a database) to the environment.
* **environment_checkpoint**: Save the current state of an environment as a container image.
### developer
This extension provides general-purpose development tools.
* **shell**: Execute shell commands in your local environment.
* **text_editor**: Perform text editing operations on local files, such as viewing, writing, or replacing strings.
* **list_windows**: List all available window titles for screen capture.
* **screen_capture**: Capture a screenshot of a display or a specific window.
* **image_processor**: Process an image file from your local disk.
### platform
This extension helps me manage my own capabilities.
* **search_available_extensions**: Search for new extensions to enhance my functionality.
* **manage_extensions**: Enable or disable extensions.
Let me know if you'd like to know more about any specific tool
Context: ○○○○○○○○○○ 0% (4754/1000000 tokens)
Upon first install, we download the dagger engine, which can take some time:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
92da235d1327 localhost/dagger-engine.dev "dagger-entrypoint.s…" 32 hours ago Up 32 hours dagger-engine.dev
70654f46f7de registry.dagger.io/engine:v0.18.10 "dagger-entrypoint.s…" 32 hours ago Up 32 hours dagger-engine-v0.18.10
I think it's the root cause of your issue atm -- please try to do: dagger -M (if you don't mind preloading the engine with our CLI) -- otherwise wait a bit more, you should see the install on docker
Btw, the UX with gemini-2.5-pro is a bit slow as in goose we don't the model thinking (personal opinion)
Oh, that’s definitely what it was, I needed to install dagger. Thanks for letting me know!
And I’ll try using a different model as well
So normally it should auto-install but it can take time. Thanks for raising that up, will write an issue to tackle that UX component 🙏
Yeah even just a UI message to let me know that it’s installing would be helpful so I know something is happening
Could you please create that issue 🙏 👼 That would be greatly appreciated ahah
Just getting back around to this thread, do you still want that issue filed?
And the part about Gemini 2.5 Pro, is it goose that doesn’t showing thinking or container-use? Not sure which part causes the slow UX
I've taken the liberty to create: https://github.com/dagger/container-use/issues/81