Unable to create cloud environment for jupyter notebook

• 

  Samantha (she/her)

  • January 04, 2022 15:57

  Hi Sabrina Camp,

  Thanks for reaching out. Can you please share a screenshot of the error you are receiving and provide the following details so we can take a closer look at your issue?
  
  

  • Terra account email address

  • Google Project ID for workspace, found on the right side of the workspace dashboard
    ​​

  • Cluster ID (visit https://app.terra.bio/#clusters, click Details, and see Name field)

  • Screenshot of your cloud environment configuration (gear icon at the top-right of workspace)

  • Approximate time issue first occurred

  
  Best,
  Samantha​

   

  0
• 

  Sabrina Camp

  • January 04, 2022 17:06
  • scamp@broadinstitute.org
  • terra-10407992
  • saturn-30f54dde-6911-4c80-8c62-c94008e53c75
  • 

  Issue started around 10 AM

  0
• 

  Samantha (she/her)

  • January 06, 2022 19:35

  Hi Sabrina,

  It looks like you are using an older version of the terra-jupyter-bioconductor image. I would suggest using the most recent version, which is us.gcr.io/broad-dsp-gcr-public/terra-jupyter-bioconductor:2.0.3. You can also just select the R/Bioconductor environment in the dropdown menu:

  

  Custom environments that extend from an older base image fail to start in time, but using custom dockers that extend from the latest base image version create successfully. The reason being that the latest images are cached so Terra isn't trying to build the environment from scratch.

  Best,

  Samantha

  0
• 

  Sabrina Camp

  • January 06, 2022 21:18

  Hi Samantha,

  I'm using an older base image intentionally. If I always use the most recent image, the packages installed would be newer/different versions which hurts the reproducibility in my research.

  I may be misunderstanding, but are you saying if I use a custom environment from an older base image version it will always time out and be unusable? Is there a workaround for this?

  Best,

  Sabrina

  0
• 

  Samantha (she/her)

  • January 11, 2022 15:41

  Hi Sabrina Camp,

  Sorry for the delayed response.

  I may be misunderstanding, but are you saying if I use a custom environment from an older base image version it will always time out and be unusable?

  Not necessarily - for older images, it depends on how big the difference is from the current cached version. If there is not much of a difference, the cloud environment will get created successfully since it doesn't need to do any extra docker pull. If there is a bigger difference between the versions, there will be more layers to docker pull which can take much longer.

  That said, your concern around reproducibility is very valid and I will bring this up with our engineers to find a solution for. I'll let you know once I have an update.

  Best,

  Samantha

  0
• 

  Sabrina Camp

  • January 18, 2022 14:44

  Hi Samantha,

  This issue did resolve itself last week. However, I am coming across this issue again this week where the environment creation times out. This happens using any custom environment. 

  Is this a known issue?

  Sabrina

  -1
• 

  Samantha (she/her)

  • January 20, 2022 15:59

  Hi Sabrina,

  Can you share a screenshot of the error? Have you tried manually deleting your cloud environment/persistent disk and creating a new one?

  Best,

  Samantha

  0

Please sign in to leave a comment.