pangeo-data/pangeo-stacks

Expose environment file from each image

rabernat opened this issue · 2 comments

As discussed in today's call, it would be great if we could download an environment.yml file for each of the docker images, to recreate the same environment locally.

Ideally this would appear on the fancy new website.

+1 from me.

The challenge here will be to determine the descriptive environment that includes the hierarchy of conda environments (repo2docker-base, pangeo/base-notebook, pangeo/pangeo-notebook) without the OS specific packages. In other words, I think this is more complicated than exporting the final environment (conda env export ...) but this would be a decent place to start.

@jhamman - After switching to GitHub Actions we're no longer updating https://pangeo-data.github.io/pangeo-stacks/ , so the environment packages seem out of date.

We are storing package lists as build artifacts, for the last PR merge
#116

The MasterBuild workflow:
https://github.com/pangeo-data/pangeo-stacks/actions/runs/36150551

Has this package list for pangeo-notebook
https://github.com/pangeo-data/pangeo-stacks/suites/445464987/artifacts/1673050

The API for accessing artifacts is here https://developer.github.com/v3/actions/artifacts/, but I think the easiest way to expose the image lists is to create a separate job called update-website runs at the end of master.yaml (https://github.com/pangeo-data/pangeo-stacks/blob/master/.github/workflows/master.yml)

accessing the lists of images like we do in the pull-request workflow:
(

- name: Download Base-Notebook Docker Image
)