RepoFlow
Error Knowledge Base DOCKER unable_to_remove_filesystem

Error: Unable to remove filesystem for <container-id>: Device or resource busy

Docker could not remove a resource because it is still in use.

Affected versions: All supported Docker Engine and Docker CLI versions.

What This Error Means

Docker could not remove a resource because it is still in use.

How to Fix It

  1. Find containers using the resource: docker ps -a (then inspect mounts as needed).
  2. Stop/remove the container(s), then retry removal.
  3. If the daemon is stuck, restart Docker and retry.

Why It Happens

  • A running container is still using the volume/filesystem layer.
  • A previous container left a stale mount or a stuck process.
  • The host OS is holding file locks (more common on desktop environments).

How to Verify

  1. Retry the remove command and confirm it succeeds.
  2. Confirm the resource no longer appears in docker volume ls / docker ps -a.

Common CLI Output

Error: Unable to remove filesystem for <container-id>: Device or resource busy

Prevention Tips

  • Clean up containers and volumes as part of CI teardown.
  • Avoid sharing volumes across many long-lived containers without clear ownership.

Where This Can Be Triggered

docs.docker.com/engine/admin/resource_constraints/

Official Docker documentation reference connected to this failure mode. - Source

Need help or found a mistake? Contact RepoFlow support for questions.

Join our mailing list