aljaz/goose
1
0
Fork 0
mirror of https://github.com/aljazceru/goose.git synced 2025-12-18 22:54:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: edits to docker guide (#1639)

Browse Source
This commit is contained in:
Angie Jones
2025-03-12 10:43:44 -05:00
committed by GitHub
parent 259ccd516e
commit bc304f0424
1 changed files with 21 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
documentation/docs/guides/goose-in-docker.md
View File

@@ -1,24 +1,26 @@
--- ---
title: Goose in Docker title: Goose in Docker
sidebar_position: 3 sidebar_position: 9
--- ---
import Tabs from '@theme/Tabs'; # Building Goose in Docker
import TabItem from '@theme/TabItem';
:::info Tell Us What You Need :::info Tell Us What You Need
There are various scenarios where you might want to build Goose in Docker. If the instructions below do not meet your needs, please contact us by replying to our [discussion topic](https://github.com/block/goose/discussions/1496). There are various scenarios where you might want to build Goose in Docker. If the instructions below do not meet your needs, please contact us by replying to our [discussion topic](https://github.com/block/goose/discussions/1496).
::: :::
# Use Case 1: Building Goose from the source in Docker
As a Goose user and developer, you can build Goose from the source file within a Docker container. This approach not only provides security benefits by creating an isolated environment but also enhances consistency and portability. For example, if you need to troubleshoot an error on a platform you don't usually work with (such as Ubuntu), you can easily debug it using Docker.
You can build Goose from the source file within a Docker container. This approach not only provides security benefits by creating an isolated environment but also enhances consistency and portability. For example, if you need to troubleshoot an error on a platform you don't usually work with (such as Ubuntu), you can easily debug it using Docker.
To begin, you will need to modify the `Dockerfile` and `docker-compose.yml` files to suit your requirements. Some changes you might consider include: To begin, you will need to modify the `Dockerfile` and `docker-compose.yml` files to suit your requirements. Some changes you might consider include:
- Setting your API key, provider, and model in the `docker-compose.yml` file. Our example uses the Google API key and its corresponding settings, but you can find your own list of API keys [here](https://github.com/block/goose/blob/main/ui/desktop/src/components/settings/models/hardcoded_stuff.tsx#L86-L94) and the corresponding settings [here](https://github.com/block/goose/blob/main/ui/desktop/src/components/settings/models/hardcoded_stuff.tsx#L67-L77).
- Changing the base image to a different Linux distribution in the `Dockerfile`. Our example uses Ubuntu, but you can switch to another distribution such as CentOS, Fedora, or Alpine.
- Mounting your personal Goose settings and hints files in the `docker-compose.yml` file. This allows you to use your personal settings and hints files within the Docker container.
Among these, only the first change is mandatory. We need to set the API key, provider, and model as environment variables because the keyring settings do not work on Ubuntu in Docker. - **Required:** Setting your API key, provider, and model in the `docker-compose.yml` file as environment variables because the keyring settings do not work on Ubuntu in Docker. This example uses the Google API key and its corresponding settings, but you can [find your own list of API keys](https://github.com/block/goose/blob/main/ui/desktop/src/components/settings/models/hardcoded_stuff.tsx) and the [corresponding settings](https://github.com/block/goose/blob/main/ui/desktop/src/components/settings/models/hardcoded_stuff.tsx).
- **Optional:** Changing the base image to a different Linux distribution in the `Dockerfile`. This example uses Ubuntu, but you can switch to another distribution such as CentOS, Fedora, or Alpine.
- **Optional:** Mounting your personal Goose settings and hints files in the `docker-compose.yml` file. This allows you to use your personal settings and hints files within the Docker container.
After setting the credentials, you can build the Docker image using the following command: After setting the credentials, you can build the Docker image using the following command:
@@ -31,19 +33,21 @@ Next, run the container and connect to it using the following command:
```bash ```bash
docker-compose -f documentation/docs/docker/docker-compose.yml run --rm goose-cli docker-compose -f documentation/docs/docker/docker-compose.yml run --rm goose-cli
``` ```
Inside the container, first try to run the following command to configure Goose:
Inside the container, run the following command to configure Goose:
```bash ```bash
goose configure goose configure
``` ```
When prompted to save the API key to the keyring, select No, as we are already passing the API key as an environment variable.
Then, you can configure Goose a second time, and this time, you can add extensions: When prompted to save the API key to the keyring, select `No`, as you are already passing the API key as an environment variable.
```bash
goose configure Configure Goose a second time, and this time, you can [add any extensions](/docs/getting-started/using-extensions) you need.
```
For example, you can add the `Developer` extension. After that, you can start a session: After that, you can start a session:
```bash ```bash
goose session goose session
``` ```
You should now be able to connect to Goose with the developer extension enabled. Follow the other tutorials if you want to enable more extensions.
You should now be able to connect to Goose with your configured extensions enabled.