Hey guys, Im trying to run orchest on AWS i did docker installation and everything seems to be fine but can't start orchest for some reason

Hey there Tarun! Thanks for getting in touch to give us some feedback, I'll take a look, give me a few minutes.

here's the result for docker image ls, I cloned it for root as well

# Installed images
"orchest/session-sidecar:latest",
"orchest/update-server:latest",
"orchest/orchest-api:latest",
"orchest/celery-worker:latest",
"orchest/file-manager:latest",
"orchest/nginx-proxy:latest",

# Additional images that do not seem to be installed
"orchest/jupyter-enterprise-gateway:latest",
"orchest/jupyter-server:latest",
"orchest/memory-server:latest",
"orchest/orchest-webserver:latest",
"orchest/auth-server:latest",
"rabbitmq:3",
"postgres:13.1",

I once had this happen when the disk got full and not all required images were downloaded

This could very well be the case here.

"Could not find the configuration file"

This could be the case because the

orchest-webserver

is not installed @Jacopo Didn't want to interrupt here, just wanted to quickly drop my thoughts :)

Yep it looks like not all images have been installed, @Tarun Singh could you check if your disk is full?

no i dont think so, so far have used only 49%

The disk is not full but I think it could very well be the case that the disk size is not enough to install Orchest. It requires about 15GBs (@Yannick do correct me if you have a better estimate)

Yes, it is probably related to disk size. We depend on the Jupyter Docker stacks, which includes images with a size of ~4GB. Explaining why Orchest could not install successfully.

@Yannick do correct me if you have a better estimate

I would guess closer to 9GB given that

orchest install

only gets you the bare minimal set of images.

ah ok ill increase the size of the disk and will keep you guys updated, thanks for the help 🙂

👍 thank you Tarun, feel free to get in touch if you need any help or have any feedback, we appreciate all of it 🙂

ah ok ill increase the size of the disk

If you want to be on the safer side I would suggest going for a disk size of 50GB given that as part of Orchest you can build custom environments (which are actually Docker containers) and that you probably want to some disk space left for files etc.

@Yannick @Jacopo I increased my memory but got this

Just so that I understand what you are getting at. Do you mean the

Could not find the configuration file.

message? If this message only popped up the very first time you successfully managed to start Orchest, then you can ignore this message (I made a small change yesterday so this message no longer pops up, but the commit is not yet included in a new release) . To check whether the configuration file is actually created you can check whether the file

$HOME/.config/orchest/config.json

exists. Hope that helps. Is Orchest running correctly now?

yes its working

Hi Tarun, we have been using

t2.large

instances with success on AWS. Smaller instances can still accommodate Orchest, it depends on what are you preferences in terms of spending vs performance.

Thanks!