hi congrats on your funding i saw it and decided to try it o

Question

hi congrats on your funding i saw it and decided to try it out however the standard installation is failing running ec2 ubuntu and your required version of docker after it starts via CLI i hit the webapp and the home ` projects` is broken stuck in loading loop chrome console showing a bunch of 500 errors for example ``` async projects session counts=true amp job counts=true 500 INTERNAL SERVER ERROR ``` ```GET 500 INTERNAL SERVER ERROR ``` ```Unable to fetch sessions Response type basic url redirected false status 500 ok false ```

Yannick · Answer

Thank you My hunch is that the volume size you chose is too small Because Orchest requires a number of Docker containers depending on installation it requires a maximum of 15GB last time I checked you need a decent volume size I recommend going for 50GB Afterwards make sure to run the installation process again If that doesn t help then please let me know Thanks for raising the issue pray

Kay Kayyy · Answer

thanks i created a new ec2 with more space and now it works would be great to add this to pre reqs in docs or display some type of error about space particularly during install time rather than run time FWIW i had 7gb free what exactly is happening where 7gb is not enough just calling an API or listing projects requires more than 7gb of disk space

Rick Lamers · Answer

Also to verify whether it s working you can run ` orchest version ext`

Rick Lamers · Answer

It s mainly the Jupyter Stacks base image required by the Jupyter Enterprise Gateway that balloon the installation size

Rick Lamers · Answer

Those are basically prebuilt images with a lot of open source data science packages This ships as the default container image in which your DS code runs

Rick Lamers · Answer

We re always looking to reduce the initial installation size but are somewhat dependent on upstream image use by the OSS we integrate

Kay Kayyy · Answer

Jupyter Notebook instead of JupyterLab

Rick Lamers · Answer

That doesn t make much difference in terms of size It s about the Docker image that provides the runtime environment for Python and R code of the user In Jupyter context that means the kernels Which are actually identical between Jupyter Notebook and JupyterLab

Kay Kayyy · Answer

another idea is instead of baking in amp integrating an entire IDE just have some plain text editor `vi` equivalent

Rick Lamers · Answer

The IDE is actually pretty lightweight It s mainly the container images that make it larger We do want to make everything more modular in the future allowing easier customization regarding what s installed by default For example we already do this for the Julia R and Python GPU base container images They re not included by default

Rick Lamers · Answer

They re pulled on use