26 replies

Sandbox Workspace Folder mapping results in errors and read only messages

✅Solved

When using a sandbox for agents, the workspace folder get mounted at /workspace.
It's source is

~/.openclaw/workspace.

~/.openclaw/workspace.

When I try to get the agent to modify the files, it reports there is a file system error and can't do it. However it is able to find the /workspace folder and read some files. When I go into the container, the ~/.openclaw/workspace folder is correctly mapped to workspace. I can modify the files in there through the bash CLI.

This is the typical error it has

sh: 1: cannot create /home/<REDACTED>/.openclaw/workspace/test.txt: Directory nonexistent

(Command exited with code 2)

sh: 1: cannot create /home/<REDACTED>/.openclaw/workspace/test.txt: Directory nonexistent

(Command exited with code 2)

If I change the workspace folder to /workspace, the agent sandbox fails as I assume it's trying to mount the nonexistant /workspace directory on the host machine.

Is there a config where you tell the sandbox agents to look at /workspace and not the other folders?

Solution

          // mount host workspace at this path INSIDE the container
          workdir: "${HOME}/.openclaw/workspace",
        },
      },
    },
  },
}

          // mount host workspace at this path INSIDE the container
          workdir: "${HOME}/.openclaw/workspace",
        },
      },
    },
  },
}

Now when the agent does:

echo hi > /home/<you>/.openclaw/workspace/test.txt

echo hi > /home/<you>/.openclaw/workspace/test.txt

…it will succeed, because that path will exist in the container (it’s the mount target).

Then recreate the sandbox so the new mountpoint applies:

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

26 replies

Dodgy490

Sandbox Workspace Folder mapping results in errors and read only messages

✅Solved

When using a sandbox for agents, the workspace folder get mounted at /workspace.
It's source is

~/.openclaw/workspace.

~/.openclaw/workspace.

sh: 1: cannot create /home/<REDACTED>/.openclaw/workspace/test.txt: Directory nonexistent

(Command exited with code 2)

sh: 1: cannot create /home/<REDACTED>/.openclaw/workspace/test.txt: Directory nonexistent

(Command exited with code 2)

Solution

          // mount host workspace at this path INSIDE the container
          workdir: "${HOME}/.openclaw/workspace",
        },
      },
    },
  },
}

          // mount host workspace at this path INSIDE the container
          workdir: "${HOME}/.openclaw/workspace",
        },
      },
    },
  },
}

Now when the agent does:

echo hi > /home/<you>/.openclaw/workspace/test.txt

echo hi > /home/<you>/.openclaw/workspace/test.txt

…it will succeed, because that path will exist in the container (it’s the mount target).

Then recreate the sandbox so the new mountpoint applies:

Jump to solution

Sandbox Workspace Folder mapping results in errors and read only messages

Similar Threads

Sandbox Workspace Folder mapping results in errors and read only messages

Similar Threads

Similar Threads

Similar Threads