I must be misunderstanding something.<p>Isn&#x27;t it Subuser that crams all the dependencies together, in one place (image)? So there was that proposal so images are deduplicated, in a sense shared files are automatically detected and stored only once, saving disk space. But then, isn&#x27;t it that Subuser is completely unaware of any metadata a particular file may have, so it can&#x27;t really tell the difference between libz and libm, or know that all those binary-different libpng16.so have the 100% compatible ABI and are interchangeable (but not all libpng12.so do)?<p>From what I understood, Subuser is a package manager (plus permission manager) that doesn&#x27;t know a thing about what it&#x27;s packaging - only the large-scale image.<p>Package managers have all libraries separate, that&#x27;s the whole point why package managers were invented in the first place. If a package management uses some database, dependencies may lay together in the filesystem, but the&#x27;re completely separate in package manager&#x27;s database. If package management system uses filesystem as its database, then packages are separate in that regard, too. There&#x27;s immutability as well, sometimes enforced, sometimes along the lines of storing `dpkg -l | grep &#x27;^ii&#x27; | awk &#x27;{ print $2 &quot;=&quot; $3 }&#x27;` output to save the exact state.