CLI Init failing on Windows 11

[Anupieslice]

I'm trying to set up Skyvern locally on Windows using Docker Desktop, but skyvern init is failing during the database migration phase.

Environment:
OS: Windows 11
Python: 3.11 (Microsoft Store version)
Setup: Local installation in .venv

The Issue: The CLI successfully starts the Postgres container and creates the DB, but crashes during "Running database migrations...". I noticed the CLI tried to switch the driver to asyncpg for Windows compatibility, but the connection still drops.

Primary Errors:
RuntimeError: no running event loop
ConnectionDoesNotExistError: connection was closed in the middle of operation
ConnectionResetError: [WinError 64]

It looks like a conflict between the Windows asyncio Proactor loop and Alembic. Has anyone seen a workaround for this on Windows? Full traceback attached.

skyvern_windows11_error.sh

[skyvern-agent]

For the CLI init issue you're experiencing on Windows 11, you can try the following troubleshooting steps:

1. Use a Different Python Version: The version from the Microsoft Store may not be fully compatible. Install Python from the official Python website and ensure you have the same version (3.11 or compatible).

2. Switch to a Different Event Loop: Set the event loop policy before running Skyvern. You can do this by adding the following lines to your script:

   import asyncio
   if sys.platform == 'win32':
       asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

3. Check PostgreSQL Connection: Confirm that your PostgreSQL service is running correctly and accessible. You can use a standalone database client to check the connection.

4. Compatibility with Alembic: Some users have reported success by downgrading Alembic. Try modifying your dependencies to use an older version that is compatible with Windows asyncio, if applicable.

5. Examine Docker Resource Settings: Ensure Docker Desktop has enough resources allocated (CPU, Memory) to run the containers smoothly.

After applying these steps, try running skyvern init again. If the issue persists, please provide any new error messages or logs for further troubleshooting. Additionally, it might be helpful to check the official Skyvern documentation on database setup for more insight [1].

Need another reply? Mention @skyvern in a comment.

Tag @skyvern to trigger a response from the agent

Diagram • Discord • GitHub

[Anupieslice]

skyvern init on Windows: Blocker bug (AttributeError) followed by Migration failure (Asyncio)
I am stuck between two distinct issues on Windows 11. I followed the suggestion to switch to the official Python 3.11.9 installer to solve a migration error, but I have now encountered a new blocker earlier in the process.

1. The Current Blocker (AttributeError):
Error: AttributeError: 'OptionInfo' object has no attribute 'replace'.
Root Cause: In skyvern/cli/init_command.py, the database_string is being passed as a typer.models.OptionInfo object instead of a string. This causes set_key to crash when attempting to write to the .env file.
Impact: I cannot complete skyvern init. A manual .env creation is not a viable workaround because the SKYVERN_API_KEY needs to be generated and synced to the database during this step.

2. The Pending Issue (Migration/Asyncio): Once the AttributeError is bypassed, I anticipate returning to the original error I reported:
Errors: RuntimeError: no running event loop and ConnectionResetError: [WinError 64].
Context: This occurs during "Running database migrations". It appears to be a conflict between the Windows ProactorEventLoop and the database driver/Alembic.

Request: Could we address the AttributeError in the CLI so that the initialization can proceed, and provide guidance on the asyncio loop policy required for Windows 11 to complete the migrations?

officialpython3_11_9_error.sh
microsoftpython3_12.sh