PR #44608: fix(docker): allow whitespace in config and workspace paths

• Repository: openclaw/openclaw
• Author: dsantoreis
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/44608

Description (problem / solution / changelog)

Windows usernames with spaces (e.g. C:\Users\John Doe) cause docker-setup.sh to bail with "OPENCLAW_CONFIG_DIR cannot contain whitespace". These are perfectly valid paths.

Problem

validate_mount_path_value rejected any path containing whitespace. On Windows with Git Bash, $HOME often resolves to a path with spaces when the Windows username contains them.

Root cause

The whitespace check was overly broad. The actual concern is YAML structure injection in the generated docker-compose file, but that only requires rejecting colons, commas, and control characters -- not spaces.

Fix

• Remove the blanket [[:space:]] rejection from validate_mount_path_value (control characters like tabs/newlines are still caught by contains_disallowed_chars)
• Relax validate_mount_spec regex to allow spaces in source/target segments (colons and commas still blocked)
• Quote volume mount strings in generated YAML so Docker Compose parses spaced paths correctly

Testing

bash -n docker-setup.sh passes. The quoting matches Docker Compose documented YAML string handling.

Fixes #44599

Changed files

• docker-setup.sh (modified, +11/-13)

---

PR #44612: fix(docker): allow whitespace in OPENCLAW_CONFIG_DIR path

• Repository: openclaw/openclaw
• Author: palomyates516-alt
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/44612

Description (problem / solution / changelog)

Fixes #44599 - OPENCLAW_CONFIG_DIR cannot contain whitespace

Root Cause

The validate_mount_path_value() function in docker-setup.sh rejected any path containing whitespace. This was overly restrictive, as Docker Compose and YAML handle quoted paths correctly.

Problem

Users on Windows with spaces in their home directory (e.g., C:\Users\John Doe) could not use the default config directory path.

Fix

Remove the whitespace check from validate_mount_path_value(). The check for control characters (newlines, tabs) is retained as those can cause parsing issues.

Test plan

• Script syntax validated
• Users can now set OPENCLAW_CONFIG_DIR to paths with spaces
• Test with path containing spaces (Windows home directory)

Changed files

• docker-setup.sh (modified, +14/-14)
• src/browser/pw-ai.ts (modified, +0/-1)
• src/browser/routes/agent.act.ts (modified, +52/-498)

---

PR #44626: fix(docker): allow whitespace in OPENCLAW_CONFIG_DIR/WORKSPACE

• Repository: openclaw/openclaw
• Author: andyliu
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/44626

Description (problem / solution / changelog)

Fixes #44599.

Summary

Allow OPENCLAW_CONFIG_DIR / OPENCLAW_WORKSPACE_DIR to contain whitespace in docker-setup.sh.

What changed

• Permit whitespace in validate_mount_path_value (still rejects control chars).
• Quote generated volume entries in docker-compose.extra.yml using YAML single-quote escaping so whitespace is preserved.
• Relax validate_mount_spec to allow whitespace while still rejecting control chars / commas and enforcing source:target[:options] shape.
• Add e2e coverage that runs docker-setup.sh with config/workspace directories containing spaces and asserts the extra compose file contains quoted mounts.

Notes

This is intended to address Windows/macOS home paths that commonly include spaces.

Changed files

• docker-setup.sh (modified, +24/-13)
• src/docker-setup.e2e.test.ts (modified, +22/-0)