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

Features/add pangeo workspace #25

Merged
merged 29 commits into from
Apr 17, 2023
Merged

Conversation

anilnatha
Copy link
Collaborator

This pull request incorporates the following notable changes:

  1. Updated how workspace dependent conda packages are installed by using an environment.yml file. Currently, the pangeo workspace is the only one that needs a custom environment.yml file that is stored at /jupyterlab3/pangeo/environment.yml. All other jupyterlab workspaces use the following /jupyterlab3/shared/environment.yml
  2. Removed /jupyterlab3-build as it is no longer needed.

* develop:
  Moving maap-py install to match vanilla
  Added Plant as part of the isce2 workspace
  Update Node JS to solve dependency issue with ISCE2
…uldn't be found during the image building process.
* develop:
  Updated R base image
  trying to update version of python
…3 dockerfile to test pangeo build with new CI pipeline.
* develop:
  Update CI image build process to allow for custom builds (#23)
* develop:
  update maap help
  locked package versions
  minor updates
  cleaned up installs
  updated extension installs
  updated jlab and dependencies versions
  update miniconda

# Conflicts:
#	jupyterlab3/docker/Dockerfile
…3 folder. This was accomplished by install a workspace dependent environments.yml file for our jupyterlab environment. Pangeo is the only environment that is currently using a custom environment.yml, all other workspaces rely on a shared environment.yml file.
Copy link
Contributor

@grallewellyn grallewellyn left a comment

Choose a reason for hiding this comment

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

Was able to build successfully locally, but I did need to add --memory 8g to be able to create the pangeo base image without a seg fault

Assuming I can build with mas.dit.maap-project.org/root/maap-workspaces/jupyterlab3/vanilla:add-pangeo-workspace, I am able to successfully build a workspace in DIT and launch/ run a jupyter notebook

@grallewellyn
Copy link
Contributor

grallewellyn commented Apr 17, 2023

After the most recent commit, trying to build this locally, I get this error:

 => ERROR [ 6/26] RUN apt-get clean && apt-get update &&     apt-get instal  2.9s
------                                                                            
 > [ 6/26] RUN apt-get clean && apt-get update &&     apt-get install -y --no-install-recommends rsync gcc python3 vim &&     apt-get clean &&     rm -rf /var/lib/apt/lists/*:                                                                       
#0 0.750 Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]           
#0 0.910 Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
#0 0.986 Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
#0 1.532 Err:1 http://deb.debian.org/debian bullseye InRelease
#0 1.532   At least one invalid signature was encountered.
#0 2.123 Err:2 http://deb.debian.org/debian-security bullseye-security InRelease
#0 2.123   At least one invalid signature was encountered.
#0 2.722 Err:3 http://deb.debian.org/debian bullseye-updates InRelease
#0 2.722   At least one invalid signature was encountered.
#0 2.768 Reading package lists...
#0 2.873 W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered.
#0 2.873 E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed.
#0 2.873 W: GPG error: http://deb.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered.
#0 2.873 E: The repository 'http://deb.debian.org/debian-security bullseye-security InRelease' is not signed.
#0 2.873 W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered.
#0 2.873 E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed.
------
ERROR: failed to solve: executor failed running [/bin/sh -c apt-get clean && apt-get update &&     apt-get install -y --no-install-recommends rsync gcc python3 vim &&     apt-get clean &&     rm -rf /var/lib/apt/lists/*]: exit code: 100

But I fixed this by doing docker system prune and then everything else ran successfully for me

@anilnatha anilnatha merged commit 7b43569 into develop Apr 17, 2023
@anilnatha anilnatha deleted the features/add-pangeo-workspace branch May 15, 2023 21:53
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.

3 participants