Docker not starting under WSL

[lucacanella]

Bug Description

Docker image ghcr.io/vectorize-io/hindsight:latest is not starting under WSL (Windows 11, Ubuntu 24.04.3 LTS) when volume is mapped on local directory.

When I run the docker image everything looks fine (i also can reach the Control Plane on localhost:9999) until "ECONNREFUSED" errors start to appear on the console.

After a while the application startup fails with the following message:

ERROR: Application startup failed. Exiting.

    | selecting default time zone ... Etc/UTC
    | creating configuration files ... ok
    | running bootstrap script ... ; stderr=2026-01-07 16:31:41.023 UTC [617] FATAL:  data directory "/home/hindsight/.pg0/instances/hindsight/data" has invalid permissions
    | 2026-01-07 16:31:41.023 UTC [617] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
    | child process exited with exit code 1
    | initdb: removing contents of data directory "/home/hindsight/.pg0/instances/hindsight/data"

Steps to Reproduce

Here is the full shell command i use to run the container:

export OPENAI_API_KEY =sk*****

docker run --rm -it --pull always -p 8888:8888 -p 9999:9999 \
  -e HINDSIGHT_API_LLM_API_KEY=$OPENAI_API_KEY \
  -v ./hindsight-docker:/home/hindsight/.pg0 \
  ghcr.io/vectorize-io/hindsight:latest

I also tried to change the permissions on the data directory (i.e. with chmod 0700 ./hindsight-docker/.pg0 -R), but wsl kept showing 777 permissions until I followed instructions from these links:

• https://www.reddit.com/r/bashonubuntuonwindows/comments/ovmlk3/unable_to_change_permissions_of_a_file_using/
• https://learn.microsoft.com/en-us/windows/wsl/file-permissions
  In particular by adding

[automount]
options="metadata"

to /etc/wsl.conf. Then I changed the permissions again and the application started.

Expected Behavior

Application runs without the need to change wsl options / configuration.

Actual Behavior

Application won't start unless wsl configuration was changed by adding

[automount]
options="metadata"

to /etc/wsl.conf, then had to manually change permissions to the mapped directory.

Version

ghcr.io/vectorize-io/hindsight:latest (07/01/2026)

LLM Provider

OpenAI

[j2h4u]

Interesting--I've had Hinsight running 24/7 under WSL 2 for two weeks now, in Docker, and everything works fine. My setup is Azure as the provider, running via Light LLM in a neighboring container