Node construction fails on Docker Toolbox

Version/Platform/Processor information (from `ipfs version --all`): ipfs version 0.4.4-dev

Type (bug, feature, meta, test failure, question): bug
Area (api, commands, daemon, fuse, etc): docker image
Priority (from P0: functioning, to P4: operations on fire): P2

Description:
I tried running the [docker image](https://hub.docker.com/r/jbenet/go-ipfs/) and I ran into issues. I could not find this issue reported anywhere else so I am reporting it here. I am available to move it somewhere else if more appropriate.

You can find the output from my terminal below. I am running this on OS X:

```
$ docker run -d --name ipfs_host -v $ipfs_staging:/export -v $ipfs_data:/data/ipfs -p 8080:8080 -p 4001:4001 -p 5001:5001 ipfs/go-ipfs:latest
Unable to find image 'ipfs/go-ipfs:latest' locally
latest: Pulling from ipfs/go-ipfs
e110a4a17941: Pull complete
8df06ff256ec: Pull complete
c49bf4128b23: Pull complete
Digest: sha256:bf2118045b8c5c464b3baee82f0cb61465169cb2f4f186017226427480a9737f
Status: Downloaded newer image for ipfs/go-ipfs:latest
26fff16d2d14a85a57f2f5cd79633313a75a08bac35f3f39cc7af5ec005a5175

$ docker logs -f ipfs_host
ipfs version 0.4.4-dev
Found IPFS fs-repo at /data/ipfs
Initializing daemon...
06:18:14.272 ERROR cmd/ipfs: error from node construction: failure writing to dagstore: fsync: invalid argument daemon.go:295
Error: failure writing to dagstore: fsync: invalid argument
```

I tried removing the IPFS config directory and that did not fix the issue.

I still don't know how to fix this but I was considering trying to change the Docker image to use the version 0.4.2 instead of the version 0.4.4-dev (and see if the problem persists).