Updates for nektar-workbook image.
Issue/feature addressed
When launching the nektar-workbook image and trying to run a Nektar++ executable from the shell, libraries such as libmpi* and libboost_*, etc, cannot be found by the dynamic linker. This is because they have been installed with Mamba and so they have been installed into /opt/conda/lib. There is a warning with libtinfo.so.6 and the version of jupyterhub needs to be updated.
Proposed solution
Add LD_LIBRARY_PATH=/opt/conda/lib to the default environment, remove libtinfo.so.6 from /opt/conda/lib and update jupyterhub version.
Implementation
In the Dockerfile to generate the nektar-workbook image we add LD_LIBRARY_PATH=/opt/conda/lib to the /etc/environment file to ensure any new shells have this variable set.
Tests
Suggested reviewers
Notes
Checklist
[ ] Functions and classes, or changes to them, are documented.[ ] User guide/documentation is updated.-
Changelog is updated. [ ] Suitable tests added for new functionality.[ ] Contributed code is correctly formatted. (See the contributing guidelines).[ ] License added to any new files.[ ] No extraneous files have been added (e.g. compiler output or test data files).
Merge request reports
Activity
changed milestone to %v5.3.0
requested review from @dmoxey
assigned to @dmoxey
added 1 commit
- e69ad0cb - Tidy up 80char width, added fix for libtinfo warning.
@dmoxey I think this is pretty much ok now. I have tested it on the running jupyerhub instance and it seems to address the issues with the path and the warning message.
- Resolved by Dave Moxey
@ccantwel Looks good to me! Think we need a changelog entry but can merge after this?
- Last reply by Chris Cantwell
mentioned in commit f27f3ba1
