Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

atlas deployments setup local results in Error: exit status 125: #2980

Closed
thenaturalist opened this issue May 31, 2024 · 2 comments
Closed

Comments

@thenaturalist
Copy link

Describe the bug
A clear and concise description of the bug.

To Reproduce
Steps to reproduce the behavior:

  1. On Mac, with Homebrew, install brew install mongodb-atlas (includes mongosh, podman) && brew tap mongodb/brew && brew install mongodb-database-tools
  2. Verify installations: mongosh 2.2.6, podman 5.1.0, mongodb/brew/mongodb-database-tools 100.9.4, mongodb-atlas-cli 1.23.0
  3. Run atlas deployments setup
  4. For What type of deployment would you like to work with? choose local
  5. For How do you want to set up your local Atlas deployment? choose default
  6. See error
Creating your cluster local8156 [this might take several minutes]
1/3: Starting your local environment...
2/3: Downloading the MongoDB binaries to your local environment...
Error: exit status 125: Error: error getting credentials - err: exit status 1, out: ``

Expected behavior
A correct and error free local deployment of Atlas as per the documentation.

Screenshots
If possible, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: macOS Sonoma 14.5 (23F79)
  • MongoCLI version 1.23.0
  • Ops Manager Version: Not applicable

Additional context
Docker is also installed on the machine but not running in any capacity at the time of running the above commands.

Copy link
Contributor

Thanks for opening this issue. The ticket CLOUDP-251808 was created for internal tracking.

@thenaturalist
Copy link
Author

Turns out cleaning my $HOME/.docker/config.json to simply {"credsStore": "osxkeychain"} did the trick.

However, I'd be surprised if most people have such a clean docker config on their machine.

Checking for config compatibility would seem like a relevant and helpful step as part of creating a deployment.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant