Skip to content

Docker Clarity #313

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

Merged
merged 6 commits into from
Oct 19, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ inputs:
<a name="enuminputs"></a>
## Enum Inputs ⚜️

For command-line flags that require a specific input as the argument, an enum type can be declared in CWL. **Specifying null here is known as long form style. It does the same thing as the question mark on the other inputs.**
For command line flags that require a specific input as the argument an enum type can be declared in CWL. **Specifying null here is known as long form style. It does the same thing as the question mark on the other inputs.**

```yaml
Format:
Expand All @@ -266,7 +266,7 @@ Format:
<a name="recordinputs"></a>
## Record Inputs 📀

For command-line flags that are either **mutually exclusive** or **dependent**, a special record type can be defined. You can also specify null here to create optional inputs.
For commandline flags that are either **mutually exclusive** or **dependent** a special record type can be defined. You can also specify null here to create optional inputs.

```yaml
#Using record inputs to create mutually exclusive inputs
Expand Down
4 changes: 2 additions & 2 deletions src/topics/using-containers.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,15 +41,15 @@ hints:
dockerPull: node:slim
```

`baseCommand: node` tells CWL that we will be running this command in a container. We
`baseCommand: node` tells CWL that we will be running this command using the Node Js runtime that is meant for Javascript files. We
then need to specify some `hints` for how to find the container we want. In this case we list
just our requirements for the docker container in `DockerRequirements`. The `dockerPull:`
parameter takes the same value that you would pass to a `docker pull` command. That is,
the name of the container image (you can even specify the tag, which is good idea for
best practices when using containers for reproducible research). In this case we have
used a container called `node:slim`.

Provide a "hello.js" and invoke `cwltool` providing the tool description and the
Create a Javascript file named "hello.js" and invoke `cwltool` providing the tool description and the
input object on the command line:

```{literalinclude} /_includes/cwl/using-containers/hello.js
Expand Down