Docker compose issues
Kinda?
I'm not sure if that FATAL error is supposed to be there. The only thing I did differently was changing the directive port: 3030:3000 in the docker compose file to expose the service on the port 3030 as 3000 is already in use on my server. However, it seems to work, maybe that FATAL is not that... fatal 😄
I see (on the documentation) that the docker compose solution is not recommended for a number of reasons, I'd like to understand why I cannot start Langfuse in the traditional docker way :/
5 Replies
I've just tried this on my machine and cannot replicate it unfortunatley, can you share your docker compose file?
mine
Langfuse worked on localhost:3030
Can you share your environment config?
Changed to port 3031 for other reasons.
By the way, Langfuse is now working, I am just a little confused on the FATAL message showing up in the logs.
If possible I'd like to go back to the Docker standard deployment, which should be more secure and stable, as stated in Langfuse doc
Ok perfect, I cannot replicate this error and have not seen it before unfortunately
Good that it is not as fatal as it sounded
Do you have issues with the production docker setup with a separate postgres db?
Docker compose is just not recommended as some folks have issues with lost postgres state when upgrading
Yes, I sent a message yesterday in the chat, just before experiencing this issue. Basically Langfuse cannot reach the DB I set up on postgres. The dedicated postgres is not on another container, but installed with apt-get
Got it, I remember the conversation. I think this is not a Langfuse specific issue but general docker networking of granting access to the port as I cannot replicate the issue via docker compose
Happy to help though if you share more details
Best case: if you have a docker compose config which replicates the issue so I can try it