-
Notifications
You must be signed in to change notification settings - Fork 3
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
Describe use of sha256 hash with Wave #448
Conversation
Thanks for actioning this @jason-seqera ! I really like the perspective you gave to this paragraph. I now actually realise it might even have a better location under the |
0d9ae5b
to
d14730f
Compare
Co-authored-by: Phil Ewels <phil.ewels@seqera.io>
docs/guide.mdx
Outdated
You can run `nextflow inspect` to find the SHA256 hash of the Wave augmented container. | ||
|
||
In your pipeline, you can use the SHA256 of the Wave augmented container, available in the target repository that you specify with the `wave.build.repository` parameter. For example: | ||
|
||
```groovy | ||
docker.enabled = true | ||
process.container = 'docker.io/<user>/my-bio-container@sha256:3235....ce8f' | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea what this means
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It comes from the discussion thread above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made no sense to me. I have rewritten it
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
Follow on from #448 Try to add a little more detail / explanation about exactly what this section is proposing.
So this is an early draft that seeks to clarify this use case.