Skip to content

Restructure the MET Dockerfiles to create images based on the new METbaseimage #2196

@jprestop

Description

@jprestop

Note: The issue was originally named "Update the MET Dockerfile to install Python 3.8.6 from source" but was changed to more accurately describe the work done.

Describe the Task

Update the MET Dockerfile to install Python 3.8.6 from source.
See https://vinodpandey.com/how-to-install-python3-on-centos-7/#installing-python-38-on-centos-7 for an example.
If this does not work well, refer to METplus’s use of conda for installing 3.8.6.

As part of this work, a new repository was created - METbaseimage - in order to handle separate versioning for the base image. This task corresponds to work on METbaseimage Issue #1 and METbaseimage Issue #3.

Time Estimate

1-3 days of work

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

MET-11.0.0-beta3 (9/14/22)

Funding Source

2702691

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Task 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 develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development 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 develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Linked issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions