---
title: "Comment by Abhinav Sharma on \"Why Docker Uses pivot_root (and Not Just chroot)\" | Hashnode"
description: "The chroot-escapes-through-open-handles point is what sells pivot_root: chroot only changes where a process thinks root is, while the old root stays mounted and"
url: "https://hashnode.com/posts/why-docker-uses-pivot-root-and-not-just-chroot/6ada0a0970561a460423373d/comment/6ada415623803b5822766e36"
---

[Discussion](https://hashnode.com/posts/why-docker-uses-pivot-root-and-not-just-chroot/6ada0a0970561a460423373d)

Comment [Why Docker Uses pivot\_root (and Not Just chroot)](https://hashnode.com/posts/why-docker-uses-pivot-root-and-not-just-chroot/6ada0a0970561a460423373d)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 22](https://hashnode.com/posts/why-docker-uses-pivot-root-and-not-just-chroot/6ada0a0970561a460423373d/comment/6ada415623803b5822766e36)

The chroot-escapes-through-open-handles point is what sells pivot\_root: chroot only changes where a process thinks root is, while the old root stays mounted and reachable, and pivot\_root actually swaps the mount so the host tree can be unmounted. Isolation by removal beats isolation by redirection.