Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python 3.9 Support #202

Merged
merged 3 commits into from
Aug 9, 2024
Merged

Python 3.9 Support #202

merged 3 commits into from
Aug 9, 2024

Conversation

mattp0
Copy link
Contributor

@mattp0 mattp0 commented Aug 8, 2024

This uses the AWS Lambda image for python 3.9
Node is set to 16.x because node 18.x and 20.x require glibc>=2.28 and 2.27 is present on amazon linux 2

Rather than try and install node 18.x or 20.x on amazon linux 2 we can keep what we had as the primary use I have seen is to deploy the cumulus dashboard.

This is a resolution to a dependency layer issue ASF encounter while building on amazon linux 2023.
Ideally once CMA can be built on python 3.12 we can update to the amazon linxu 2023 and use python 3.12 and node 20.x

@mattp0
Copy link
Contributor Author

mattp0 commented Aug 8, 2024

This has been tested on the NISAR upgrade and the ASF upgrade and the dependency issues are resolved.

# Uncommenting fixes: `fatal: detected dubious ownership in repository at '/CIRRUS-core'
# Uncommenting fixes: `fatal: detected dubious ownership in repository at '/CIRRUS-DAAC'
# COPY .gitconfig /.gitconfig
RUN python3 -m pip install boto3 setuptools
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is probably not needed as IIRC boto3 comes on the amazon images

Dockerfile Outdated Show resolved Hide resolved
Dockerfile Outdated Show resolved Hide resolved
@mattp0 mattp0 force-pushed the mrp/feature/18.3.1.1 branch 2 times, most recently from 24445e5 to af41998 Compare August 8, 2024 23:17
Copy link
Contributor

@mckadesorensen mckadesorensen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. It might be a good idea to request Mike and Chris on this since it is a change to CIRRUS-core.

@mattp0
Copy link
Contributor Author

mattp0 commented Aug 9, 2024

big question here is, does moving back to node 16.x in the build image effect any of the users ? otherwise the experience will be the same. python 3.9 on an amazon linux 2 container. https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

@mattp0 mattp0 merged commit 4da6741 into master Aug 9, 2024
2 checks passed
@mattp0 mattp0 deleted the mrp/feature/18.3.1.1 branch August 9, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants