-
Notifications
You must be signed in to change notification settings - Fork 212
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
Porter unable to install bundle and giving rpc errors #2473
Comments
Hi there, thanks for reporting your issue. Do you mind to share which version of porter you are using and the porter command you ran that produced this error? |
By default, if you do not configure differently in ~/.porter/config.yaml, Porter will use the mongodb-docker storage plugin, which runs a mongo container on porter 27018 named
Can you check your porter configuration file (located in ~/.porter, named config.toml or config.yaml or config.json) and verify that you do not have a storage plugin set? Then run One cause of that error is that porter was unable to start the mongo container and then it fails to connect. |
@nitishdsharma Sorry for lack for reply, because the issue is so old and the version of Porter is old, I will close it. If you are still having problems please create a new issue. |
Creating a new porter bundle and trying to install it locally but its rendering rpc errors on porter install command.
Error messages
rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] } could not retrieve the installation record: could not read storage schema document: rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] } could not retrieve the installation record: could not read storage schema document: rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] }
The text was updated successfully, but these errors were encountered: