ab304c9fe8
* fix(scripts): handle docker-init failures gracefully for private registry The make docker-init command was failing on Linux environments when users could not access the private Volces container registry. This commonly occurs in corporate intranet environments with proxies or for users without registry credentials. Changes: - Detect sandbox mode from config.yaml before attempting image pull - Skip image pull entirely for local sandbox mode (default) - Gracefully handle pull failures with informative messages - Update setup-sandbox Makefile target with same error handling Fixes #1168 * Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: BillionClaw <billionclaw@users.noreply.github.com> Co-authored-by: Willem Jiang <willem.jiang@gmail.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| check.py | ||
| check.sh | ||
| cleanup-containers.sh | ||
| config-upgrade.sh | ||
| configure.py | ||
| deploy.sh | ||
| docker.sh | ||
| serve.sh | ||
| start-daemon.sh | ||
| tool-error-degradation-detection.sh | ||
| wait-for-port.sh | ||