Description

Edit: this issue misunderstands the command's purpose, see the last paragraph.

I wanted to mount a directory, which the machine I am on only has read-access to, into the container, via nemoclaw container_name share mount.
However, when I did, I got the error:

  SSHFS mount failed.
  fusermount3: user has no write access to mountpoint <path of local directory I wanted to mount>

I wanted OpenClaw to be able to access the directory in read-only mode as well, similar to what is asked in #1045. Copying the files over is infeasible.

Reproduction Steps

Run nemoclaw container_name share mount, targeting a directory within a read-only filesystem.

(Also note that these lines automatically prevent you from sharing another mounted filesystem entirely, but that is a secondary problem and not as relevant)

Environment

• OS: AlmaLinux 9.7
• Node: v24.15.0
• Docker: version 29.4.2, build 055a478
• Nemoclaw: v0.0.36

Debug Output

Logs

Checklist

• I confirmed this bug is reproducible
• I searched existing issues and this is not a duplicate

Edit

I have misunderstood the purpose of the nemoclaw sandbox_name share mount command. I expected it to be designed primarily for bi-directional file sharing, which is why I tried to use it to mount a directory into the sandbox. However, as it is only supposed to mount (parts of) the sandbox file system onto the host machine (which, because it's now mounted, allows for changes from the host machine, thus "bidirectional"), this was never designed to work.

The PR #3235 sums it up very well in the sample error that will be output in my case once it's merged: […]parent filesystem is read-only. share mount projects sandbox files onto a host directory via SSHFS, so the local target must be on a writable filesystem. […]

I apologize for the misunderstanding; I am happy to close this issue once the error message is improved, such as in the PR.