Closed isontheline closed 4 years ago
Disclaimer: i'm not a gitpod staff, but i think that i know what is causing this.
On my end it seems to take a long time if Dockerfile.gitpod
is used with an instructions that configures additional packages or other configuration that is expected to be present as addition to the used docker image since it seems that gitpod configures these on runtime.
I believe that this can be optimized by providing a custom Dockerfile in Dockerfile.gitpod
as:
FROM gitpod/workspace-full:latest
GitPod has documentation on submiting these images here: https://www.gitpod.io/docs/42_config_docker/#creating-docker-images-for-gitpod
@Kreyren Thanks for your tip :) But I don't use a Dockerfile.gitpod file. The workspace is as simple as possible.
@isontheline If you tried yesterday evening: We had some "users" abusing Gitpod to mine their cryptocurrency with a new tool. It took us some time to detect, implement detection routines and deploy those.
@geropl Ok I will try again tonight and will let you know Thank you !
@geropl It's better than yesterday :
I'm closing this issue. Thanks for your work Gitpod!
Describe the bug Everytime I launch a workspace I need to wait 4 to 6 minutes in order to have my workspace alive :(
To Reproduce Create a workspace, wait at least one week and then try to launch it.
Expected behavior I expect my workspace launched in less than 60 seconds. If greater than 60 seconds I prefer to start my old Eclipse IDE instead. This delay is always, even if the workspace has been paused one hour ago.
Additional Information
Does this load is normal every time I start my workspace ?