Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: Browser container running but not exposed [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#58606•Fetched 2026-04-08 02:00:17
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
hershkoyhershkoy
Participants
hershkoyhershkoy
Timeline (top)
labeled ×1

After setting up the sandbox browser using ./scripts/sandbox-browser-setup.sh, the browser container starts successfully but is not exposed or detected by the OpenClaw gateway.

Root Cause

After setting up the sandbox browser using ./scripts/sandbox-browser-setup.sh, the browser container starts successfully but is not exposed or detected by the OpenClaw gateway.

Code Example

./scripts/sandbox-browser-setup.sh
Started services via Docker Compose

---

docker ps -a
CONTAINER ID   IMAGE                                    COMMAND                  CREATED          STATUS                   PORTS                                                                     NAMES
c8d21ae76790   openclaw-sandbox-browser:bookworm-slim   "sleep infinity"         42 minutes ago   Up 42 minutes            5900/tcp, 6080/tcp, 9222/tcp                                              openclaw-sbx-agent-main-f331f052
519ea69aa608   openclaw:local                           "docker-entrypoint.s…"   24 hours ago     Up 5 minutes (healthy)   0.0.0.0:18789-18790->18789-18790/tcp, [::]:18789-18790->18789-18790/tcp   openclaw-openclaw-gateway-1

---

docker compose exec openclaw-gateway openclaw browser status
profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: chromium
detectedPath: /usr/bin/chromium
running: false
browser: unknown
CDP expected at 127.0.0.1:18800
RAW_BUFFERClick to expand / collapse

Summary

After setting up the sandbox browser using ./scripts/sandbox-browser-setup.sh, the browser container starts successfully but is not exposed or detected by the OpenClaw gateway.

Problem to solve

Environment

  • OpenClaw version: 2026.3.27
  • Setup method: ./scripts/sandbox-browser-setup.sh
  • Docker: (add your version if needed)
  • OS: (add your OS if relevant)

What I did

Ran:

./scripts/sandbox-browser-setup.sh
Started services via Docker Compose

Checked containers:

docker ps -a

Current Behavior Containers

docker ps -a
CONTAINER ID   IMAGE                                    COMMAND                  CREATED          STATUS                   PORTS                                                                     NAMES
c8d21ae76790   openclaw-sandbox-browser:bookworm-slim   "sleep infinity"         42 minutes ago   Up 42 minutes            5900/tcp, 6080/tcp, 9222/tcp                                              openclaw-sbx-agent-main-f331f052
519ea69aa608   openclaw:local                           "docker-entrypoint.s…"   24 hours ago     Up 5 minutes (healthy)   0.0.0.0:18789-18790->18789-18790/tcp, [::]:18789-18790->18789-18790/tcp   openclaw-openclaw-gateway-1

Browser container is running However, ports (e.g. 9222) are not exposed to host

Gateway status

docker compose exec openclaw-gateway openclaw browser status
profile: openclaw
enabled: true
running: false
transport: cdp
cdpPort: 18800
cdpUrl: http://127.0.0.1:18800
browser: unknown
detectedBrowser: chromium
detectedPath: /usr/bin/chromium
running: false
browser: unknown
CDP expected at 127.0.0.1:18800```



### Proposed solution

Make the ports exposed so that we can connect to them from outside the container (and see what the agent is doing)

### Alternatives considered

_No response_

### Impact

It affects usability. 

### Evidence/examples

_No response_

### Additional information

_No response_

extent analysis

TL;DR

Exposing the ports of the browser container to the host machine is likely necessary to allow the OpenClaw gateway to detect it.

Guidance

  • Verify that the Docker Compose configuration used by ./scripts/sandbox-browser-setup.sh exposes the necessary ports (e.g., 9222) from the container to the host.
  • Check the docker-compose.yml file for the ports directive to ensure it maps the container's ports to the host's ports.
  • Use the docker inspect command to check the container's network settings and verify that the ports are exposed as expected.
  • Consider using the docker-compose exec command to verify that the ports are accessible from within the container.

Example

No specific code example is provided due to the lack of detailed configuration files in the issue.

Notes

The exact steps to expose the ports may depend on the specific Docker Compose configuration and version used. Ensure that the ports directive in the docker-compose.yml file is correctly configured to map the container's ports to the host's ports.

Recommendation

Apply a workaround by manually exposing the necessary ports using the docker-compose.yml file or the docker run command with the -p option to map the container's ports to the host's ports. This is because the current setup does not expose the ports as required for the OpenClaw gateway to detect the browser container.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#tensor shape#autograd error#model save/load

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING