Merge branch 'master' into v2.4

Author: vsoch

README.md

@@ -91,6 +91,7 @@ very large images (e.g., ~3600 down to ~1800). A few notes on the inputs shown a
 
 `docker2singularity` uses the Docker daemon located on the host system. It will access the Docker image cache from the host system avoiding having to redownload images that are already present locally.
 
+
 If you ever need to make changes, you can easily export the squashfs image into either a sandbox folder or ext3 (legacy) image, both of which have writable.
 
 ```
@@ -164,6 +165,10 @@ You can also use `--writable` and convert an ext3 image into a production image:
 ```
 sudo singularity build ext3.img production.simg
 ```
+### Contributed Examples
+The following are a list of brief examples and tutorials generated by the Singularity community for using **docker2singularity**. If you have an example of your own, please [let us know](https://www.github.com/singularityware/docker2singularity/issues)!
+
+ - [docker2singularity-demo](https://github.com/stevekm/docker2singularity-demo): an example of using docker2singularity on MacOS and using Vagrant to test the output Singularity image, complete with notes and a nice Makefile.
 
 
 ## Tips for making Docker images compatible with Singularity
@@ -205,6 +210,5 @@ If you are getting `WARNING: Non existant bind point (directory) in container: '
      -m "/shared_fs /custom_mountpoint2" \
      ubuntu:14.04
 
-
 ## Acknowledgements
 This work is heavily based on the `docker2singularity` work done by [vsoch](https://github.com/vsoch) and [gmkurtzer](https://github.com/gmkurtzer). Hopefully most of the conversion code will be merged into Singularity in the future making this container even leaner!