Closed AmanSal1 closed 7 months ago
Feel free to ignore the temporal containers. At present those are only relevant if you're doing batched exports.
@mariusandra So should I proceed with the development guide and ignore this error ? Thanks in advance
Unless you're planning on doing batched exports locally, yes.
@mariusandra Sorry for disturbing you again but I am running posthog on codespaces but I am unable to see the UI at the localhost port 8000 ? I have to different terminal running one for docker and other for starting all the services.
Unfortunately we're not able to provide basic debugging support π
Bug description
So I am trying to compile PostHog locally on my VirtualBox, which has an Ubuntu OS. I'm following the steps outlined in the development guide, but when I run the command "docker compose -f docker-compose.dev.yml up", everything compiles correctly except for one thing: the PostHog Temporal UI isn't getting the port. I thought this issue might be due to running it on VirtualBox, so I attempted to do it on CodeSpaces. However, I encountered the same error
How to reproduce
1.Follow the development guide and after running the command "docker compose -f docker-compose.dev.yml up" error pops up
Environment
docker compose
, version/commit: [please provide]Additional context
Error log on codespaces
Thank you for your bug report β we love squashing them!