# FUSE remove

> Tag 3: the server removes a file or an empty directory of the mount the client serves live, by the path of the entry within the mount; the client answers with exactly one channel response, ok, read only, or an error.

Canonical: https://protocol.diverge.network/2.3.0/container-proxy-endpoints/fuse-mount/server/remove/
Specification revision: 2.3.0

The server opens this channel when a program in the container performs
the operation on the mount. The ask names the entry by its path
within the mount, and names no mount: the scope is the mount.

- **The request.** The tag byte `3` followed by the ask.
  [Request](/2.3.0/container-proxy-endpoints/fuse-mount/server/remove/request/) states its form.
- **The response.** Exactly one channel response and the channel
  response finish. [Response](/2.3.0/container-proxy-endpoints/fuse-mount/server/remove/response/) states the
  sequence.
- **The meaning.** What the ask means, and what its answer means,
  [FUSE remove](/2.3.0/endpoints/containers-agents-run/server/fuse-remove/) states; the client relays the ask
  to its client with the mount's id in front of it.
- **No repetition.** The server sends the ask exactly once. A channel
  that ends without a finish, and a channel response finish that no
  channel response precedes, are reported to the program as the
  operation failed.