You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,12 @@ Replace `D:\host\path\where\to\output\singularity\image` with a path on the host
24
24
25
25
`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.
26
26
27
+
### Contributed Examples
28
+
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)!
29
+
30
+
-[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.
31
+
32
+
27
33
## Tips for making Docker images compatible with Singularity
28
34
29
35
- Define all environmental variables using the `ENV` instruction set. Do not rely on `.bashrc`, `.profile`, etc.
@@ -61,6 +67,7 @@ If you are getting `WARNING: Non existant bind point (directory) in container: '
61
67
singularityware/docker2singularity \
62
68
-m "/shared_fs /custom_mountpoint2" \
63
69
ubuntu:14.04
64
-
70
+
71
+
65
72
## Acknowledgements
66
73
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!
0 commit comments