Skip to content
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

GenAI changes to allow it to run on Debian GNU/Linux unstable #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HaakonME
Copy link

I needed a few changes to make GenAI work on my Debian GNU/Linux unstable. If this is interesting to you, perhaps you can turn it into --profile debian-unstable option?

Cheers,
Haakon


docker compose up --build --force-recreate
docker-compose up --build --force-recreate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't docker-compose deprecated for docker compose ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"docker compose" is the updated version from Docker, yes. However, in the latest version of Debian GNU/Linux and the Unstable branch, it is still a separate command for "docker" and "docker-compose". That is why I suggested, if possible, to create an extra profile, e.g. --profile debianunstable, rather than assume every Linux can use --profile linux. I do not know if this is possible, but it would be nice. As a general rule, "docker compose", with the space is the updated way. I hope this helps.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I meant is we should encourage the use of docker compose. But if it is available on Debian Unstable, why not use it ?

Anyway, the changes you made should work even when using docker compose (the context: . is implicit in docker compose, don't know for docker-compose). The only thing I would do differently is creating another start script for the old docker-compose instead of changing the actual one.

I would still be interested in what error you had before, maybe there is another workaround!

@oskarhane
Copy link
Collaborator

Thanks!
What's the issue you're experiencing?

Also, the start.sh file should be removed so need to edit that (it's a leftover from early days).

@HaakonME
Copy link
Author

HaakonME commented Oct 16, 2023

@oskarhane , the issue is that there is a difference between official Docker and official Debian unstable packages for Docker, the latter contains docker without compose and a separate command called docker-compose. I am not sure if this means means Docker v1 vs Docker v2, but the PR and the .env below resolved the issue for me on Debian unstable, so maybe it can help someone else.

Note to someone else: using the LLM below will take quite some time to fetch in the background, probably several minutes - be patient.


#OPENAI_API_KEY=sk-...
#OLLAMA_BASE_URL=http://host.docker.internal:11434
OLLAMA_BASE_URL=http://llm:11434
NEO4J_URI=neo4j://database:7687
NEO4J_USERNAME=neo4j
NEO4J_PASSWORD=password
#LLM=llama2 #or any Ollama model tag, or gpt-4 or gpt-3.5
LLM=llama2-uncensored:7b
EMBEDDING_MODEL=sentence_transformer #or openai or ollama

LANGCHAIN_ENDPOINT="https://api.smith.langchain.com"
LANGCHAIN_TRACING_V2=true # false
LANGCHAIN_PROJECT=#your-project-name
LANGCHAIN_API_KEY=#your-api-key ls_...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants