Closed computermechanic closed 1 month ago
Hi @computermechanic, thanks for reporting this. @yidant, could you look into whether there is a bug in the 14.2.2 and 14.2.3 containers?
Is there any upate or any work around for the issue?
Hi @computermechanic ! Thanks for following up! The bug probably results from the lack of a package 'gettext'. It affects some of the users. I'm currently facing another issue with a module. I'll update the containers after I solve it and let you know.
If you want to use 14.2.2 and 14.2.3 right now, you can pull 14.3.0 containers instead and build the 14.2.2/14.2.3 GCHP with the environment. The containers later than 14.3.0 have this package installed.
I will close out this issue now since using newer GCHP version containers fixes the problem.
Name and Institution (Required)
Name: Edward So Institution: The Chinese University of Hong Kong, ITSC, Research Computing Team
Confirm you have reviewed the following documentation
Description of your issue or question
Please provide as much detail as possible. Always include the GCHP version number and any relevant configuration and log files.
I have follow the following containers guide to setup the environment to run GCHP: https://gchp.readthedocs.io/en/stable/supplement/containers.html
Everythings is fine in both 14.2.0 and 14.2.1 but I got a problem when using 14.2.2 and 14.2.3. After I use the containers to create the run directory, I found that the run directory is not well setup. Most of the .rc files (GCHP.rc,ExtData.rc,HEMCO_Config.rc, etc.) is not present in the run directory. Also the setCommonRunSettings.sh script is a blank script. Is there any way to solved the problem of the run directory created by 14.2.2 and 14.2.3 container?