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

Captain crashes on new server if registry is not set up #2057

Open
khromov opened this issue May 8, 2024 · 1 comment
Open

Captain crashes on new server if registry is not set up #2057

khromov opened this issue May 8, 2024 · 1 comment

Comments

@khromov
Copy link

khromov commented May 8, 2024

Not sure if I'm doing something wrong but I observed on multiple server that if you install the server, don't setup a local registry (it's not required and not part of the onboarding) then try to create an app, the app will create but the captain service crashes and restarts. The app settings exist but no "placeholder" image is deployed. It would be better if you were not allowed to create an app before setting a default registry.

@githubsaturn
Copy link
Collaborator

This definitely not required for a single server application.

Check out the demo instance (password: captain42)
https://captain.server.demo.caprover.com/#/login

What is the exact repro steps:
1- Install CapRover normally on a VPS
2- Run caprover serversetup
3- Create a new app
4- Watch it crash?

Do you do anything specific by any chance?

Also, do you have the logs for when this happens?

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