Skip to content

Local quickstart and repo install not working #5756

Description

@AlexMili

Hi,

Started from a fresh install in a fresh env (python 3.11.14) and tried to install skyvern using the quickstart but got an error while running it on macOS:

> skyvern quickstart
╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 🚀 Starting Skyvern Quickstart                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────╯

Initializing Skyvern...
╭────────────────────────────────────────╮
│ Welcome to Skyvern CLI Initialization! │
╰────────────────────────────────────────╯
This wizard will help you set up Skyvern.
Would you like to run Skyvern locally or in the cloud? [local/cloud]: local
╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ PostgreSQL Setup                                                                                     │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────╯
🐳 PostgreSQL is already running in a Docker container.
✅ Database user exists.
✅ Database exists.
📊 Running database migrations...
Alembic mode:  online
Alembic: no running loop
Error during quickstart: (sqlite3.OperationalError) table organizations already exists
[SQL:
CREATE TABLE organizations (
        organization_id VARCHAR NOT NULL,
        organization_name VARCHAR NOT NULL,
        webhook_callback_url TEXT,
        max_steps_per_run INTEGER,
        created_at DATETIME NOT NULL,
        modified_at DATETIME NOT NULL,
        PRIMARY KEY (organization_id)
)

]
(Background on this error at: https://sqlalche.me/e/20/e3q8)

Here a simple CREATE TABLE IF NOT EXISTS would solve it but it's not working out of the box.

Also tried to run a pip install . after cloning the repo but got a version conflict:

ERROR: Cannot install skyvern and skyvern==1.0.31 because these package versions have conflicting dependencies.

The conflict is caused by:
    skyvern 1.0.31 depends on jinja2<4 and >=3.1.2
    litellm 1.83.14 depends on jinja2==3.1.6
    skyvern 1.0.31 depends on python-dotenv<2 and >=1.0.0
    fastmcp 3.2.0 depends on python-dotenv>=1.1.0
    litellm 1.83.13 depends on python-dotenv==1.0.1
    litellm 1.83.12 depends on python-dotenv==1.0.1
    litellm 1.83.11 depends on python-dotenv==1.0.1
    litellm 1.83.10 depends on python-dotenv==1.0.1
    litellm 1.83.9 depends on python-dotenv==1.0.1
    litellm 1.83.8 depends on python-dotenv==1.0.1
    litellm 1.83.7 depends on jinja2==3.1.6

Additionally, some packages in these conflicts have no matching distributions available for your environment:
    jinja2
    python-dotenv

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions