Full docker-compose deployment

[Fosowl]

This is the issue for integration of a full docker-compose deployment of AgenticSeek.

Goal -> Deploy all agenticSeek services:

• redis
• searxng
• frontend
• backend

Currently the start_services.sh (which use docker-compose) allow to deploy all services beside backend. The backend service is currently commented out in docker-compose.yml.

PR #154 by tcsenpai is a preview of current attempt to fix and include backend service in deployment.

Internal ports:

• 6379 -> redis
• 8080 -> searxng
• 3000 -> frontend
• 8000 -> backend host ports (host.docker.internal extra hosts):
• 11434 -> ollama
• 1234 -> lm-studio

Some consideration:

• We would have to have other "standard" port to support other llm provider. For example if someone use llama.cpp server they would need to know what port is supported.

• Backend should have outbound internet access needed for remote APIs provider and "server" provider.

• The work_dir will need to be an environment variable. The config.ini would have work_dir = ${WORK_DIR}.

• The docker for backend would need to mount the work_dir folder from the host. We need a way to ensure that work_dir is not a root folder or overly large folder (should not mount /, C:\system32 or similar). Perhaps the ./start_services.sh script could check the work_dir path and size before running docker-compose

• All readme would need to be updated according to change. For example having WORK_DIR as an environment variable instead of defined in config.ini would need to be explained.

• How to make text to speech work if running inside docker ?

[sammcj]

This is exciting to see, keep up the great work! 🚀

[itJunky]

I already have worked version with backend and addition nginx proxy containers. Proxy need to correct routing requests between api.py and searxnd and frontend

https://github.com/itJunky/agenticSeek/tree/devops

[eyshoteam]

I have a full working version and some extra ikle admin ui etc

[Fosowl]

@eyshoteam @itJunky You will have to coordinate on discord with TCsenpai in #containerization channel, putting the backend on docker is easy, the hard part is not having a service randomly crash, not relying on chrome bundle which can get deprecated, and having the work folder mounted with safety mechanism and transfer back to host on files change

[itJunky]

i'm already ccordinate with TCsenpai and he have no time for continue developing agenticseek. @Fosowl You need to choose one of us to continue. I'm not using discord(blocked in our country), only telegram.

It's doesn't crash and correct mounts of working dir and other files like config.

[Fosowl]

How did you contact him if you don't have discord and why didn't he notice me ? yeah it's a bit hard to tell whenever he gave up or just have a life I will try to get in touch with him and reassign the task if he gave up

[itJunky]

By telegram

[Fosowl]

Sorry I pursued the task because it was quite urgent and there was some considerations to take into account that neither of you seems to take into account. I am currently working on the task on the docker_deployement branch.

[plitc]

Dockerfile.backend fixes (full working setup) #265 https://github.com/Fosowl/agenticSeek/issues/265

[Fosowl]

Backend containerization has been merged to main in https://github.com/Fosowl/agenticSeek/pull/298. tested by @antoineVIVIES and myself. readme updated.