I can't seem to run the project on Docker with CUDA (GTX 1070): Failed to connect to database

Open
#370 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker, go
Domain
database, devops

Research direction

Start by comparing the Docker command and setup described in issue #273 with the configuration used here, then trace the startup path through the database connection error. Reproduce the failure with Docker and CUDA if possible; done means identifying the cause of the database-file failure and documenting or fixing the supported setup.

Written by the indexing model from the issue text.

Description

Hi,

I'm trying to run the project on Docker and I'm getting the error:

=== Scriberr Container Setup ===
Requested UID: 0, GID: 0
Setting up custom user with UID=0, GID=0...
Group with GID 0 already exists, using it
Warning: Could not change user ID, continuing with existing user
Setting up data directories...

=== Setup Complete ===
Switching to user appuser (UID=0, GID=0) and starting application...
time=05:00:02 level="INFO " msg="Starting Scriberr" version=dev
[+] Loading configuration
time=05:00:02 level="INFO " msg="Registering adapters with environment path" whisperx_env=/app/whisperx-env
time=05:00:02 level="INFO " msg="Adapter registration complete"
[+] Connecting to database
time=05:00:02 level=ERROR msg="Failed to connect to database" error="failed to connect to database: unable to open database file: out of memory (14)"

I don't know why, I'm trying to run the file with the command you mentioned here:
https://github.com/rishikanthc/Scriberr/issues/273

Dominant language
Go
Stars
3.1k
Forks
264
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rishikanthc/Scriberr

All issues in rishikanthc/Scriberr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.