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

Cloning a dolt repo onto a virtual machine #5344

Closed
nilswachsmuth-imtf opened this issue Feb 10, 2023 · 4 comments
Closed

Cloning a dolt repo onto a virtual machine #5344

nilswachsmuth-imtf opened this issue Feb 10, 2023 · 4 comments

Comments

@nilswachsmuth-imtf
Copy link

Hi Dolt team,

We are trying to use dolt on a virtual machine. After dolt status we get that we are on the main branch, so dolt is installed. However, when we try to clone the needed dolt repo we get the following error:

Screenshot error message dolt

Any chance we can get some help on this?

Thanks a lot!!

@nilswachsmuth-imtf
Copy link
Author

We also checked the credentials. Using ‘dolt creds ls’, we see that we use credentials that are linked to our account.

@fulghum
Copy link
Contributor

fulghum commented Feb 10, 2023

Hey @nilswachsmuth-imtf, thanks for reaching out. We're happy to help. Could you run dolt version and let us know what version of the Dolt command line you're using on that virtual machine? The error about unsupported repo format (__DOLT__) makes me think there might be an out of date version.

It looks like you are using DoltLab, so I'm also tagging @coffeegoddd as well just in case he sees any other clues.

@coffeegoddd
Copy link
Contributor

@nilswachsmuth-imtf I sent an email with my proposed fix. I believe this has to do with the versions of DoltLab and Dolt you are using. Please upgrade to the latest DoltLab and Dolt and let me know if the problem persists. The DoltLab docker-compose.yaml file should have the -allow-nbf-dolt flag set in the doltlabremoteapi block.

@timsehn
Copy link
Sponsor Contributor

timsehn commented Feb 10, 2023

I'm going to close this. Please reopen if the issue persists after upgrade.

@timsehn timsehn closed this as completed Feb 10, 2023
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

4 participants