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

Containers that require a long time to load respond with a 500 error when accessed #107

Open
stolpeo opened this issue Sep 27, 2021 · 1 comment
Milestone

Comments

@stolpeo
Copy link
Contributor

stolpeo commented Sep 27, 2021

Containers that require a long time to load respond with a 500 error. Be more clear. How to distinguish? When a container is running and not yet available, display a warning or similar. Maybe use a threshold?

@stolpeo stolpeo added this to the Backlog milestone Sep 27, 2021
@january3
Copy link
Member

january3 commented Oct 7, 2021

I think that the first (and easiest) thing to do would be to give a meaningful error message, like you said: "container is working, but cannot connect to its port XXXX. Container has been up XXX minutes (if XXX < 1h, then it is possibly still initializing)".

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

No branches or pull requests

2 participants