# Adding HDF5: Tree Hash Mismatch! (A Docker-on-Windows problem; solved)

**URL:** https://discourse.julialang.org/t/adding-hdf5-tree-hash-mismatch-a-docker-on-windows-problem-solved/35817
**Category:** General Usage
**Tags:** package, windows, hdf5, docker
**Created:** [March 11, 2020, 12:04am UTC](https://discourse.julialang.org/t/adding-hdf5-tree-hash-mismatch-a-docker-on-windows-problem-solved/35817 "2020-03-11T00:04:46Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![staticfloat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/staticfloat/32/34_2.png) [@staticfloat](https://discourse.julialang.org/u/staticfloat)
#### Post date: [March 11, 2020, 9:12pm UTC](https://discourse.julialang.org/t/adding-hdf5-tree-hash-mismatch-a-docker-on-windows-problem-solved/35817/8 "2020-03-11T21:12:21Z")

</div>

> Just to check: there’s nothing in the package installer using symlinks, right? I know those don’t work out on mounted drives from Windows.

Unfortunately, we use symlinks extensively within Linux packages, since they save a lot of space when packages want to have libraries named (for instance) `libfoo.so.1.2.3.`, `libfoo.so.1` and `libfoo.so` all at once.

> The Docker doesn’t “remember” installed packages, so that’s why I mounted a directory for it to store packages in in the first place.

You can try declaring a docker volume; instead of bridging something over from your host filesystem, you can just create a named volume. I don’t know for sure what Docker will do there, but I would hope that it would choose the simpler option and not store it in a windows filesystem.

---

_[View the full topic](https://discourse.julialang.org/t/adding-hdf5-tree-hash-mismatch-a-docker-on-windows-problem-solved/35817)._