-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker rock for survival package #2
Comments
Thanks, I will certainly make use of that 😀 Maybe my question should have been, is this the correct home for a survival analysis image, rather than one that is in a "demo" repo? |
dsSurvival package is not in the official Datashield's Github. You should build and publish your own image, using this example. If you do so, I'll use it in opal-demo.obiba.org in place of this demo one. |
I was wondering what is the plan if an docker image is needed which contains both dsMediation, dsExposome and dsSurvival? |
We can't do all combinations, then it is up to the consortium to make their own images. And they would probably use a private docker repo, just like Inesctec does with Coral for Recap. |
Yes although it might be nice for consortia to share to reduce work?
…On Thu, 16 Jun 2022, 17:15 Yannick Marcon, ***@***.***> wrote:
We can't do all combinations, then it is up to the consortium to make
their own images. And they would probably use a private docker repo, just
like Inesctec does with Coral for Recap.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBAPNRFC4QNCVXJPLRJW3LVPNG57ANCNFSM5Y7EUNAQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
And yes I can see that I should create my image in the Github where the package has been created... |
You could have the |
Yes that sounds like a good idea.
And then if I build an image, can it live in the DataSHIELD docker hub
account (like for omics and exposome)? Or is this where we need some kind
of audit?
…On Thu, 16 Jun 2022, 19:55 Yannick Marcon, ***@***.***> wrote:
You could have the Dockerfile within your R package source repo, for user
reference. Just declare it in a .Rbuildignore file so that it does not
get packaged.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBAPNXEMKQDPLHUWVN7NV3VPN2B5ANCNFSM5Y7EUNAQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
omics and exposome should be in https://hub.docker.com/u/brgelab space. You should have your own as well. |
Ok great - I'll do that
…On Fri, 17 Jun 2022, 10:54 Yannick Marcon, ***@***.***> wrote:
omics and exposome should be in https://hub.docker.com/u/brgelab space.
You should have your own as well.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBAPNWBNPJY2NK4IHKYHA3VPRDKZANCNFSM5Y7EUNAQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
dsSurvival is in new profile "dolomite-beach" |
Is this the repo I should use to create a Rock image for survival analysis?
The text was updated successfully, but these errors were encountered: