a new faq and a small addition to the Docker faq#35
a new faq and a small addition to the Docker faq#35vsoch merged 2 commits intosingularityware:masterfrom GodloveD:add-a-faq
Conversation
| ### When I try mounting my container with the ```-B``` or ```--bind``` option I receive an <i>unknown option</i> or <i>Invalid argument</i> error. | ||
|
|
||
| Make sure that you are using the most recent Singularity release to mount your container to the host system. Also, make sure you are using an up-to-date Singularity to bootstrap your container. Some features (such as ```--bind```) will not work in earlier versions. | ||
|
|
There was a problem hiding this comment.
I really like this addition - I (still) run into this from time to time, but because I put the --bind in the wrong spot! Should we add a bit about that as well? Something like:
Make sure that you are using the most recent Singularity release to mount your container to the host system, and that the --bind argument is placed after the execution command (e.g, run, exec, shell). An example might look like this:
singularity run -B $PWD:/data analysis.img ...
What do you think, something like that? Then I think we are good to go!
|
Yes I definitely think that addition would be helpful. I'm not too familiar
with GitHub and it's associated etiquette yet. Shall I make the change or
do you want to? And is it enough to push a commit to the same branch or do
I need to fiddle with the pull request? Thanks for your patience.
…On Dec 10, 2016 3:03 PM, "Vanessa Sochat" ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pages/docs/overview/faq.md
<#35 (review)>
:
> @@ -227,6 +229,9 @@ Additionally, there are precautions within the container context to mitigate any
You can read more about the Singularity <a href="/docs-security">security overview here</a>.
+### When I try mounting my container with the ```-B``` or ```--bind``` option I receive an <i>unknown option</i> or <i>Invalid argument</i> error.
+
+Make sure that you are using the most recent Singularity release to mount your container to the host system. Also, make sure you are using an up-to-date Singularity to bootstrap your container. Some features (such as ```--bind```) will not work in earlier versions.
I really like this addition - I (still) run into this from time to time,
but because I put the --bind in the wrong spot! Should we add a bit about
that as well? Something like:
Make sure that you are using the most recent Singularity release to mount
your container to the host system, and that the --bind argument is placed
after the execution command (e.g, run, exec, shell). An example might look
like this:
singularity run -B $PWD:/data
What do you think, something like that? Then I think we are good to go!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHUUXC0qCEjWi_8OO_fvDq_n9cVlJtJkks5rGwWfgaJpZM4LJsgb>
.
|
|
oh you will love Github! When you make a pull request (PR) you can keep pushing to the same branch (in this case, |
|
Thanks! Okie Dokie.
…On Sat, Dec 10, 2016 at 3:16 PM, Vanessa Sochat ***@***.***> wrote:
oh you will love Github! When you make a pull request (PR) you can keep
pushing to the same branch (in this case, add-a-faq) and it will update
automatically (and this is the most common and easiest option). The other
case is sometimes done, but a little harder - I would basically pull your
branch, make an addition, and then make a PR to your PR, and then merge
this PR, or (if you aren't available) submit a new PR with the combined
changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHUUXOR9d2xb3B3GT8nqVc-gqo9S79Jfks5rGwi6gaJpZM4LJsgb>
.
|
|
Looks great! Thanks for updating this, I've run into this issue several times. |
|
Hey just in case this broke the site, I'm going to revert. Don't worry - will be added again if it wasn't the issue! |
|
I emailed Github support, going to get to the bottom of the index bug - will re-merge yours back when we do. Sorry about this! |
|
All good ☺
…On Dec 10, 2016 4:54 PM, "Vanessa Sochat" ***@***.***> wrote:
I emailed Github support, going to get to the bottom of the index bug -
will re-merge yours back when we do. Sorry about this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHUUXCmqIlo1XBBR6VU9GvFVZkqHAiECks5rGx-AgaJpZM4LJsgb>
.
|
|
ok, bug is fixed, and now your section is live again! The bug was with the new github pages - if you read that post, it's supposed to ignore the |
|
Ah. Guess that's on of the risks of living on the edge. Thanks for letting
me know what the trouble was.
…On Dec 10, 2016 7:39 PM, "Vanessa Sochat" ***@***.***> wrote:
ok, bug is fixed, and now your section is live again
<http://singularity.lbl.gov/faq#when-i-try-mounting-my-container-with-the--b-or---bind-option-i-receive-an-iunknown-optioni-or-iinvalid-argumenti-error>
!
The bug was with the new github pages
<https://github.com/blog/2289-publishing-with-github-pages-now-as-easy-as-1-2-3>
- if you read that post, it's *supposed to* ignore the README.md given
that you have an index.md or index.html, however when you add a jekyll
layer on top of that, methinks we found a bug in their stuff somewhere,
because we had an index.md (which I changed to index.html to test) and it
still rendered the README.md
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHUUXNIpRVo2RE7jbTXgwmXkF7GUEN2Yks5rG0YsgaJpZM4LJsgb>
.
|
2 participants
No description provided.