fix(container): Add container env, polish doc

Author: kr11

build/Dockerfile.videxserver

@@ -1,12 +1,10 @@
-# Thanks to Daniel Black for providing a great packaging example.
-
-
 FROM python:3.9-slim
 
 ENV PYTHONDONTWRITEBYTECODE=1 \
     PYTHONUNBUFFERED=1 \
     PIP_DISABLE_PIP_VERSION_CHECK=1 \
     PIP_NO_CACHE_DIR=1 \
+    VIDEX_CONTAINER=1 \
     PYTHONPATH=/opt/videx/src
 
 WORKDIR /opt/videx

build/videx_container_entrypoint.py

@@ -1,6 +1,5 @@
-#!/usr/bin/env python3
 """
-VIDEX Docker entrypoint.
+VIDEX container entrypoint.
 
 This entrypoint provides two modes:
 - `server`: start the long-running VIDEX stats server (default)
@@ -28,6 +27,10 @@ def _in_container_best_effort() -> bool:
     Best-effort heuristics to detect container environment.
     Used only for warnings (never for rewriting args or failing).
     """
+    explicit = os.environ.get("VIDEX_CONTAINER")
+    if explicit and explicit.strip().lower() not in {"0", "false", "no"}:
+        return True
+
     if os.path.exists("/.dockerenv"):
         return True
 
@@ -124,8 +127,8 @@ def _maybe_warn_localhost_target(argv: List[str]) -> None:
 
     sys.stderr.write(
         "Warning: You may be running in a container, but the `--target` parameter is configured with 127.0.0.1/localhost.\n"
-        "         In Docker, localhost usually refers to the container itself.\n"
-        "         If your MariaDB/VIDEX runs on the Docker host, this may fail.\n\n"
+        "         In a container, localhost usually refers to the container itself.\n"
+        "         If your MariaDB/VIDEX runs on the host machine, this may fail.\n\n"
         "Suggestions:\n"
         "  - Docker Desktop (Mac/Windows): try host.docker.internal in --target.\n"
         "  - Linux Docker Engine: add this when running the container:\n"

doc/VIDEX_SERVER_DOCKER.md

@@ -2,11 +2,7 @@
 
 The latest public image is:
 
-- `kangrongme/videx-server:0.2.0` (Docker Hub)
-
-Make sure your environment can reach Docker Hub. If Docker Hub is not accessible but GHCR is, use:
-
-- `ghcr.io/kr11/videx-server:0.2.0`
+- `ghcr.io/bytedance/videx-server:0.2.0-preview-test1` (GHCR)
 
 This image supports two entrypoint modes:
 
@@ -42,7 +38,7 @@ Expose container port `5001` to a host port (choose any free host port, like 500
 ```bash
 docker run -d --name videx-server \
   -p 5001:5001 \
-  kangrongme/videx-server:0.2.0
+  ghcr.io/bytedance/videx-server:0.2.0-preview-test1
 ```
 
 Then open:
@@ -60,7 +56,7 @@ Then open:
 
 ```bash
 docker run --rm --name videx-sync \
-  kangrongme/videx-server:0.2.0 sync \
+  ghcr.io/bytedance/videx-server:0.2.0-preview-test1 sync \
   --target <TARGET_HOST>:<TARGET_PORT>:<TARGET_DB>:<TARGET_USER>:<TARGET_PASS> \
   [--videx <VIDEX_HOST>:<VIDEX_PORT>:<VIDEX_DB>:<VIDEX_USER>:<VIDEX_PASS>] \
   [--videx_server <VIDEX_SERVER_HOST>:<VIDEX_SERVER_PORT>]
@@ -80,7 +76,7 @@ Run:
 
 ```bash
 docker run --rm --name videx-sync \
-  kangrongme/videx-server:0.2.0 sync \
+  ghcr.io/bytedance/videx-server:0.2.0-preview-test1 sync \
   --target 203.0.113.42:15508:tpch_tiny:videx:password \
   --videx 203.0.113.42:15508:videx_tpch_tiny:videx:password \
   --videx_server 203.0.113.42:5001
@@ -110,7 +106,7 @@ Inside a container, `localhost/127.0.0.1` refers to the container itself. If Mar
 ```bash
 docker run --rm --name videx-sync \
   --add-host=host.docker.internal:host-gateway \
-  kangrongme/videx-server:0.2.0 sync \
+  ghcr.io/bytedance/videx-server:0.2.0-preview-test1 sync \
   --target host.docker.internal:<PORT>:<DB>:<USER>:<PASS> \
   --videx host.docker.internal:<PORT>:<VIDEX_DB>:<VIDEX_USER>:<VIDEX_PASS> \
   --videx_server host.docker.internal:<VIDEX_SERVER_PORT>