-
Notifications
You must be signed in to change notification settings - Fork 360
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
uvicorn error upon running ./run_skyvern.sh #319
Comments
@devinat1 is your postgres configured to require a password for all user roles? We have a known issue with our setup script in situations like that. Our setup script currently creates a passwordless user, which often fails on Linux (Ubuntu) because the default postgres has password required on new dbs |
I guess this is caused by the reason that he tried to mix-use docker and local Skyvern. Our docker-compose will create the DB directory in the |
I didn't alter any of the setup script, so the default configuration exists (clone then run setup.py, with poetry installed through https://python-poetry.org/docs/ with |
You'd better choose one way to set up, by docker or local. |
It wasn't me mixing, but rather I tried locally, then tried via docker compose thereafter. It would be good if one ran without interfering with the other, since in practice it is difficult to uninstall the local install. |
Yeah, we will figure it out. Or if you're familiar with docker, you can try to set up the postgres in another directory, or as an individual container. |
Ok, I ran the command
|
Oh, man. You didn't start any DB. |
So should I run the ./setup.sh script again to have the DB recreated? |
I don't how you run the DB previously. |
I am getting the following upon running
./run_skyvern.sh
on Ubuntu 22.04:This is after a successful ./setup.sh script run.
The text was updated successfully, but these errors were encountered: