Skip to content

Commit

Permalink
docs(logbook): update day 6 (got docker working)
Browse files Browse the repository at this point in the history
  • Loading branch information
amyheather committed Jul 26, 2024
1 parent 647dd1a commit cb716e4
Showing 1 changed file with 24 additions and 1 deletion.
25 changes: 24 additions & 1 deletion logbook/posts/2024_07_26/index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -182,4 +182,27 @@ However, I now got a new error:
ERROR conda.cli.main_run:execute(125): `conda run /bin/bash -c jupyter-lab /home/code/` failed. (See above for error)
```

This was unexpected, as now the file matches exactly to the functional Dockerfile used for Shoaib et al. 2022, except for that it is `environment.yaml` and the environment name.
This was unexpected, as now the file matches exactly to the functional Dockerfile used for Shoaib et al. 2022, except for that it is `environment.yaml` and the environment name.

I tried changing the environment channel back to `defaults`, rebuilt on local machine, recorded versions.

```
name: lim2020
channels:
- defaults
- conda-forge
dependencies:
- numpy=1.19.1
- pandas=1.1.1
- python=3.8.5
- ipykernel=6.28.0
- matplotlib=3.5.1
- pytest=7.4.4
- jupyterlab=4.0.11
```

Built docker image. Still failed as before. It appears it's not using the settings from the `jupyter_notebook_config.py` as that sets allow root as True, but the error is that running as root is not recommended that we can use --allow-root to bypass.

Tried switching to conda-forge again. No difference.

[Based on this post](https://discourse.jupyter.org/t/running-jupyter-server-from-a-docker-container/23537), I tried adding `notebook` to the environment and then re-running. And then it worked! Tested running the model: all fine.

0 comments on commit cb716e4

Please sign in to comment.