-
Notifications
You must be signed in to change notification settings - Fork 26
Description
Describe the Problem
In testing METplus, George has found that running ncdump inside a MET Docker container often doesn't work. Instead it errors out. In testing, we have found that it's related to how the NetCDF, HDF4, and HDFEOS libraries are compiled. Recommend updating the Dockerfile to install HDF and HDFEOS into subdirectories of /usr/local and then ensure that ncdump still runs fine.
Once fixed, consider retagging MET version 9.1 so that ncdump is functional within that image.
Expected Behavior
The ncdump utility should run on all valid NetCDF files within the MET docker container.
Environment
Describe your runtime environment:
1. Machine: Docker Container
2. Software version number(s): images for version number met-9.1, develop, and likely others
To Reproduce
Describe the steps to reproduce the behavior:
docker pull dtcenter/met:9.1
docker create --name medium_range dtcenter/metplus-data:3.1-medium_range
docker run --rm -it --volumes-from medium_range dtcenter/met:9.1
ncdump -h /data/input/METplus_Data/model_applications/medium_range/grid_to_obs/netcdf/nam/conus_sfc/prepbufr.nam.20170601.t00z.tm00.nc
Relevant Deadlines
None.
Funding Source
None.
Define the Metadata
Assignee
- Select engineer(s) or no engineer required: John HG (George to review PR)
- Select scientist(s) or no scientist required: No scientist required
Labels
- Select component(s)
- Select priority
- Select requestor(s)
Projects and Milestone
- Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
- Select milestone to relevant bugfix version
Define Related Issue(s)
Consider the impact to the other METplus components.
- METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy
Direct impact on METplus, but no issue required there.
Bugfix Checklist
See the METplus Workflow for details.
- Complete the issue definition above, including the Time Estimate and Funding Source.
- Fork this repository or create a branch of main_<Version>.
Branch name:bugfix_<Issue Number>_main_<Version>_<Description>
- Fix the bug and test your changes.
- Add/update log messages for easier debugging.
- Add/update unit tests.
- Add/update documentation.
- Push local changes to GitHub.
- Submit a pull request to merge into main_<Version>.
Pull request:bugfix <Issue Number> main_<Version> <Description>
- Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project(s), Milestone, and Linked issues - Iterate until the reviewer(s) accept and merge your changes.
- Delete your fork or branch.
- Complete the steps above to fix the bug on the develop branch.
Branch name:bugfix_<Issue Number>_develop_<Description>
Pull request:bugfix <Issue Number> develop <Description>
- Close this issue.