6.4.12 | docker pull icr.io/ibmz/jupyter-notebook@sha256:fde98431eaebd594b5840c7bb152a9e7091b110bf167c22ecf06f3f66b274b53 | Vulnerability Report | 10-29-2024 | 6.5.3 | docker pull icr.io/ibmz/jupyter-notebook@sha256:b03c7ba80c15b5782d089c1fafa7cf53197291096388d8bd44fae9b0dedbe244 | Vulnerability Report | 10-29-2024 | 6.4.8 | docker pull icr.io/ibmz/jupyter-notebook@sha256:a1852b4031665b7e7419099d173b52457d2c351dd0e06d797c5c17fa24fbc260 | Vulnerability Report | 10-29-2024 | v7.0.0a2 | docker pull icr.io/ibmz/jupyter-notebook@sha256:42bff78ca394db7649f66da77024be7173e9d8b973f7fece4606ce3a547be23c | Vulnerability Report | 04-05-2022 | 6.4.5 | docker pull icr.io/ibmz/jupyter-notebook@sha256:365348625a953abf8110262251de02620a8b98e6118b4898054993c7013fb4a5 | Vulnerability Report | 10-29-2024 |
Version | Pull String | Security (IBM Cloud) | Created |
---|---|---|---|
8888
so these ports must be exposed when issuing the docker run:
docker run --rm -it -p 8888:8888 icr.io/ibmz/jupyter-notebook:6.4.5 -ip 0.0.0.0
The server should now be accessible at the IP of your system on port 8888, but will require an authorization token to log in. By checking the logs you can find the access token to use.
http://YOUR_SYSTEM_IP:8888/?token=4af405f0407002fe3d636e8727cd0939bef99ca4a2176dad
It is worth noting that the ip flag is not specified here, as it's assumed that 'localhost' has been replaced in the mounted config
docker run --rm -it -p 8888:8888 -v myvolume:/home/notebooks icr.io/ibmz/jupyter-notebook:6.4.5
docker run --rm -it -p 8888:8888 -e NBDIR=/home/ANOTHERDIR icr.io/ibmz/jupyter-notebook:6.4.5 -ip 0.0.0.0