You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Previous versions of this documentation suggested running the ``latest`` tag of the image. For reproducibility, we are now asking
@@ -65,8 +65,8 @@ The ``-p`` flag to Docker maps a TCP port in the container to a TCP port on the
65
65
66
66
### Image Name and Tag (Version)
67
67
68
-
The final line of the Docker command above: ``dbmi/4ce-analysis:version-2.3.0`` specifies the image name and tag that will be run.
69
-
The image name is ``dbmi/4ce-analysis`` and the tag is the string following the colon, e.g. ``version-2.3.0``.
68
+
The final line of the Docker command above: ``dbmi/4ce-analysis:version-2.4.0`` specifies the image name and tag that will be run.
69
+
The image name is ``dbmi/4ce-analysis`` and the tag is the string following the colon, e.g. ``version-2.4.0``.
70
70
We will use tags to track the version of the container that each site is running locally.
71
71
We will attempt to keep this documentation up-to-date with instructions for running the latest release version, but you can
72
72
always refer to the container's registry page https://hub.docker.com/repository/docker/dbmi/4ce-analysis/tags?page=1 for
@@ -169,7 +169,7 @@ connect to the container.
169
169
A final option is to run the container in a way that directly presents the user with an interactive R session. The container will stop after you quit this R session. Note, this command runs the container so you can't already have one running when issuing it. The --rm flag will ensure that when the R session is quit, the container is stopped and cleaned up.
170
170
171
171
```bash
172
-
docker run --name 4ce -v /SOME_LOCAL_PATH:/4ceData --rm -it dbmi/4ce-analysis:version-2.3.0 R
172
+
docker run --name 4ce -v /SOME_LOCAL_PATH:/4ceData --rm -it dbmi/4ce-analysis:version-2.4.0 R
173
173
```
174
174
175
175
@@ -183,7 +183,7 @@ In more detail, the steps are are follows:
183
183
184
184
### 1. On the *bastion* host: Pull the container image from the registry
0 commit comments