Skip to content

Update 07-containers.md #78

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.

Sign up for GitHub

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 1 commit into from
Jan 18, 2018
Merged

Update 07-containers.md #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 7 additions & 2 deletions _episodes/07-containers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ automatically, allowing you to use Docker to simplify your software
management while avoiding the complexity of invoking and managing Docker
containers.

One of the responsibilities of the CWL runner is to adjust the paths of
input files to reflect the location where they appear inside the container.


This example runs a simple Node.js script inside a Docker container.

*docker.cwl*
Expand Down Expand Up @@ -67,10 +71,11 @@ Final process status is success
{: .output}

Notice the CWL runner has constructed a Docker command line to run the
script. One of the responsibilities of the CWL runner is to adjust the paths of
input files to reflect the location where they appear inside the container.
script.

In this example, the path to the script `hello.js` is `/home/me/cwl/user_guide/hello.js`
outside the container but `/var/lib/cwl/job369354770_examples/hello.js` inside
the container, as reflected in the invocation of the `node` command.


[docker]: https://docker.io