Skip to content

Remove image reference for openclaw sandbox #370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
artberger merged 1 commit into from
May 22, 2026
Merged

Remove image reference for openclaw sandbox #370

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions src/blogContent/nemoclaw-kagent-sandbox-secure-production-imp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,6 @@ metadata:
namespace: kagent
spec:
backend: openclaw
image: us-docker.pkg.dev/field-engineering-us/images/openshell/openclaw-sandbox:adf18c0-netif-amd64
modelConfigRef: default-model-config
description: "my openclaw agent"

Expand Down Expand Up @@ -116,7 +115,6 @@ kubectl -n kagent create secret generic telegram-credentials \
namespace: kagent
spec:
backend: openclaw
image: us-docker.pkg.dev/field-engineering-us/images/openshell/openclaw-sandbox:adf18c0-netif-amd64
modelConfigRef: default-model-config
description: "my openclaw agent"
channels:
Expand Down Expand Up @@ -144,4 +142,4 @@ Jensen mentioned at the latest GTC keynote:

>OpenClaw is like the Operating System for personal AI

It allows anyone to run, build, and orchestrate as many Agentic environments as they'd like, and these Agentic environments can be anything from a banking agentic to a healthcare agentic to a full suite of multi-agent workloads running within any and every environment. The orchestration layer for where the Agents and sandboxes run in Kubernetes, but what the Agent does can be for anything and everything outside of Kubernetes.
It allows anyone to run, build, and orchestrate as many Agentic environments as they'd like, and these Agentic environments can be anything from a banking agentic to a healthcare agentic to a full suite of multi-agent workloads running within any and every environment. The orchestration layer for where the Agents and sandboxes run in Kubernetes, but what the Agent does can be for anything and everything outside of Kubernetes.
Loading