chore(docs): Info on using local resources/troubleshooting podman macos #11
Conversation
|
|
||
| The hostnames are: | ||
| * host.containers.internal (podman) | ||
| * host.docker.internal (docker) |
There was a problem hiding this comment.
As author I'll add a note that it seems recent versions of podman do also support the docker host ( containers/podman#19361 )but I've left the text as-is for now
Signed-off-by: Nigel Jones <[email protected]>
|
Squashed, rebased, & made consistent with fix in #10 |
|
ping @jezekra1 |
| If you are a developer on `bee-api` or `bee-ui` and want to run only the supporting infrastructure, | ||
| use the profile `infra`, e.g.: | ||
|
|
||
| ```shell | ||
| docker compose --profile infra up -d | ||
| ``` | ||
| ### Connecting to host resources |
There was a problem hiding this comment.
Please move this to troubleshooting guide
The generic comments are not necessary we only need to access host for ollama, the guide is organized by error messages, please add it under the specific error message which occurs when you cannot connect to ollama.
You can also improve the error message in ./bee-stack.sh directly
|
|
||
| Below is an example `.env` configuration for a podman environment which will allow the bee stack to connect back to ollama running on the host | ||
| ``` | ||
| LLM_BACKEND=ollama |
There was a problem hiding this comment.
Please remove this section, this is already in example.env and it's configured automatically with the ./bee-stack.sh script
Two suggestions for readme as a followon to PR #10
I've added links to the reference docs, and given an example of hostnames that work in the default case. However there are many potential combinations...
I've also added an explicit config example - this depends on the earlier PR being an acceptable fix.
I hit issues with podman-compose, and added workaround to the readme. One other option is to consider removal of the ulimit spec in compose, but at least by adding a doc note that could be considered separately