File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -138,7 +138,7 @@ For a Dockerfile to work on Binder, it must meet the following requirements:
138
138
${NB_USER}
139
139
```
140
140
141
- This is the user that will be running the jupyter notebook process
141
+ This is the user that will be running the JupyterLab process
142
142
when your repo is launched with binder. So any files you would like to
143
143
be writeable by the launched binder notebook should be owned by this user.
144
144
@@ -166,7 +166,7 @@ For a Dockerfile to work on Binder, it must meet the following requirements:
166
166
5 . It must accept command arguments. The Dockerfile will effectively be launched as:
167
167
168
168
``` shell
169
- docker run < image> jupyter notebook < arguments from the mybinder launcher>
169
+ docker run < image> jupyter lab < arguments from the mybinder launcher>
170
170
```
171
171
172
172
where {}` <arguments ...> ` includes important information automatically set by the binder
@@ -189,7 +189,7 @@ You can build and test your image locally like this.
189
189
2 . Try starting a container from the image.
190
190
191
191
``` shell
192
- docker run -it --rm -p 8888:8888 my-image jupyter-notebook --ip=0.0.0.0 --port=8888
192
+ docker run -it --rm -p 8888:8888 my-image jupyter-lab --ip=0.0.0.0 --port=8888
193
193
```
194
194
195
195
3 . Inspect the container from terminal.
You can’t perform that action at this time.
0 commit comments