feat: add Docker support #1072 #1073
Conversation
There was a problem hiding this comment.
what is this file for? i think we can remove it
There was a problem hiding this comment.
Yeah, I think goose decided this was the right way to communicate the pr description, will remove
documentation/docker.md
Outdated
There was a problem hiding this comment.
i think we can remove this file
Dockerfile
Outdated
| @@ -0,0 +1,29 @@ | |||
| # Build stage | |||
| FROM rust:1.75 as builder | |||
There was a problem hiding this comment.
Goose generated this file, I'm fiddling with it as it appears there are some other deps when attempting to retrieve credentials
blevz
force-pushed
the
feature/docker-support
branch
from
7ec9784 to
d1eb1ff
Compare
|
hitting this error with the created image, is there a way to build the cli w/o that functionality? Failed to create provider: Failed to access keyring: Platform secure storage failure: DBus error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory |
|
You should be able to bind mount it from host os but usually people don't do that as dbus is for desktop only. |
|
I looked into the code a bit . You usually define feature in Cargo.toml file and you can choose what feature to enable / disable at completion with those. It seems like Goose has not done that so this might be a bit of a larger effort as you have to define split code functionality in the codebase and use features to tell the compiler what code path to include during build |
This commit adds Docker support to goose via a multi-stage Dockerfile that: - Uses rust:1.75 for building - Uses debian:bookworm-slim for runtime - Includes required system dependencies - Provides documentation for Docker usage The Docker image allows running goose without installing Rust locally and provides a consistent runtime environment.
blevz
force-pushed
the
feature/docker-support
branch
from
d1eb1ff to
c919a19
Compare
|
Got it working |
| # Copy the binary from builder | ||
| COPY --from=builder /usr/src/goose/target/release/goose /app/goose | ||
|
|
||
| ENV GOOSE_KEYRING_BACKEND=file |
There was a problem hiding this comment.
i don't think this env exists. you'd wanna set the keys as env vars when running the container
https://block.github.io/goose/docs/troubleshooting/#keychainkeyring-errors
There was a problem hiding this comment.
docker run -ti --rm --entrypoint=/bin/bash \
-e DATABRICKS_HOST="$DATABRICKS_HOST" \
-e DATABRICKS_TOKEN="$DATABRICKS_TOKEN" \
goose
|
@blevz this Dockerfile is working & i left a comment on how you can use it. We don't wanna officially support the Docker route right now so I am close out this PR for now. |
So goose + claude on openrouter basically one shotted this...
This commit adds Docker support to goose via a multi-stage Dockerfile that:
The Docker image allows running goose without installing Rust locally and provides a consistent runtime environment.