12 Replies
Containers can have more than one image. And you are running a postgres image in addition to the app when you run docker-compose. But I'm actually still wrong because you're not touching the image in workers.
I'm running postgres elsewhere (Google Cloud SQL)
also, I've never seen anyone ever run multiple images in a single container
I think you might be confusing multi-stage builds?
Maybe I'm not a docker expert. https://github.com/langfuse/langfuse/blob/main/docker-compose.yml
Is this considered a multi-stage build or more than image per container?
GitHub
langfuse/docker-compose.yml at main · langfuse/langfuse
🪢 Open source LLM engineering platform. Observability, metrics, evals, prompt management 🍊YC W23 🤖 SDKs + integrations for Typescript, Python, OpenAI, Langchain, LlamaIndex, Litellm - langfuse/lang...
docker compose is spinning up multiple containers
thats multiple images in multiple containers orchestrated by compose
technically you can shove two images into the same namespaces, except for the filesystem namespace, and in theory that "should" work, but yeah I've never seen anyone do that in real life. Definitely not supported for anyone sane 😛
Aight thanks for the clarification, I will live to not misinform another day
everyone gotta start somewhere 😐 my first day on langfuse/analytics for AI/LLMs so I know nothing of it yet 🙂
haha all good, I have about 6 years of experience researching sandboxing and containers in general.
ask me about an obscure Linux security thing, I probably know about it 😛
Similar, started with lxc, openvz etc. Jumped to the docker bandwagon a while back. Now I'm 99% containers and ansible.
Nice! My experience is also in bypassing/breaking sandboxing too.
Clarification, currently you only need one container to use Langfuse. We'll introduce additional containers in the next major release for increased scalability and background tasks. I'll write a small summary of what's next for langfuse soon