[bug?] - container environment not detected / log file permissions issue

[kquinsland]

With the container images pushed, I have this working in a k8s cluster with one small issue.

On start up, this is all I see in the logs

╔══════════════════════════════════════╗                                                                                                                                                 
║  onWatch v2.10.0                     ║                                                                                                                                                 
╠══════════════════════════════════════╣                                                                                                                                                 
║  Providers: copilot                  ║                                                                                                                                                 
║  API:       github.com/copilot (β)   ║                                                                                                                                                 
║  Polling:   every 2m0s              ║                                                                                                                                                  
║  Dashboard: http://localhost:9211    ║                                                                                                                                                 
║  Database:  /data/onwatch.db         ║                                                                                                                                                 
║  Auth:      admin / ****            ║                                                                                                                                                  
╚══════════════════════════════════════╝                                                                                                                                                 
                                                                                                                                                                                         
Copilot Token:     <...>                                                                                                                                                     
                                                                                                                                                                                         
Error: failed to open log file for daemon: open /data/.onwatch.log: permission denied      

I am not precisely sure why this is happening but before I dive in / spend a ton of time running a few experiments, I wanted to ask if there was a way to explicitly disable logging to a file / log directly to std{out,err}.

[prakersh]

Root cause identified: The container environment detection (IsDockerEnvironment()) only checks for /.dockerenv (Docker-specific) and DOCKER_CONTAINER env var. Kubernetes pods using containerd/CRI-O don't have /.dockerenv, so the detection fails and the daemon fork logic runs inappropriately.

Immediate workaround: Add --debug to your container command to run in foreground mode — this skips daemonization entirely and logs to stdout, which is the expected behavior for containers:

command: ["onwatch", "--debug"]

Alternatively, set DOCKER_CONTAINER=1 in your pod's environment variables.

I'll fix this properly by adding Kubernetes detection (checking for KUBERNETES_SERVICE_HOST env var or /var/run/secrets/kubernetes.io/serviceaccount). Thanks for the report!

[prakersh]

Fixed in v2.10.1: https://github.com/onllm-dev/onWatch/releases/tag/v2.10.1

The container image is building now - should be available in a few minutes. You can then update your k8s deployment to use ghcr.io/onllm-dev/onwatch:v2.10.1 (or :latest).

No need for --debug or DOCKER_CONTAINER=1 workarounds anymore - onWatch will now properly detect your Kubernetes environment and run in foreground mode automatically.

Let me know if it works for you :)