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

Use GDAL >=3.6 for k8s JupyterHub Image #35

Closed
scottyhq opened this issue Dec 6, 2022 · 1 comment · Fixed by #40
Closed

Use GDAL >=3.6 for k8s JupyterHub Image #35

scottyhq opened this issue Dec 6, 2022 · 1 comment · Fixed by #40
Assignees

Comments

@scottyhq
Copy link
Contributor

scottyhq commented Dec 6, 2022

GDAL has built-in cloud credential session handling that previously did not work well with K8s. Basically opening s3://bucket/raster.tif would end up with 'Unable to open' or other credential-related errors, see OSGeo/gdal#4058 for details.

If you use GDAL>=3.6 (rasterio>=1.3.4) accessing data stored in S3 via rasterio and GDAL should be smoother.

cc @tsnow03 @fperez @weiji14

@weiji14
Copy link
Member

weiji14 commented Dec 6, 2022

If you use GDAL>=3.6 (rasterio>=1.3.4) accessing data stored in S3 via rasterio and GDAL should be smoother.

I will say that GDAL=3.6 packages have been a broken mess on conda-forge recently, see e.g. conda-forge/qgis-feedstock#276 and conda-forge/fiona-feedstock#202. Best to wait until the dust settles a bit 🙂

@yuvipanda yuvipanda moved this to 📋 Backlog in March 2023 Event Jan 20, 2023
@weiji14 weiji14 self-assigned this Feb 21, 2023
@weiji14 weiji14 moved this from 📋 Backlog to 🏗 In progress in March 2023 Event Feb 22, 2023
weiji14 added a commit that referenced this issue Feb 23, 2023
Refresh conda-forge packages listed in the `environment.yml` file to use
those with GDAL3.6 builds.

Fixes #35
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in March 2023 Event Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants