W
Wasp2mo ago
prof_mark

deleted my docker image with and can't recreate

I deleted my docker image that was running the db. I ran wasp start db and it made a new db, but now when i connect with
wasp start
wasp start
(after running
wasp start db
wasp start db
), I get the following error on the db
2024-10-31 07:13:44.454 UTC [40] ERROR: relation "public.Session" does not exist at character 98
2024-10-31 07:13:44.454 UTC [40] STATEMENT: SELECT "public"."Session"."id", "public"."Session"."expiresAt", "public"."Session"."userId" FROM "public"."Session" WHERE ("public"."Session"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
2024-10-31 07:13:44.454 UTC [40] ERROR: relation "public.Session" does not exist at character 98
2024-10-31 07:13:44.454 UTC [40] STATEMENT: SELECT "public"."Session"."id", "public"."Session"."expiresAt", "public"."Session"."userId" FROM "public"."Session" WHERE ("public"."Session"."id" = $1 AND 1=1) LIMIT $2 OFFSET $3
2 Replies
kapa.ai
kapa.ai2mo ago
Hi @prof_mark. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- It seems you're encountering an issue with your Wasp database after deleting and recreating the Docker image. The error message suggests that the Session table doesn't exist in your database, which typically indicates that the database schema is not up to date. To resolve this issue, you need to run database migrations. In Wasp, migrations are usually applied automatically when you start the app, but in this case, it seems they weren't applied correctly. Here's what you can try: 1. First, make sure your database is running:
wasp start db

wasp start db

2. Then, instead of just wasp start, try running the migrations explicitly:
wasp db migrate-dev

wasp db migrate-dev

3. After the migrations are applied successfully, try starting your app again:
wasp start

wasp start

If the issue persists, you might need to check if there are any pending migrations or if the database was created correctly. You can try to reset the database completely: 1. Stop all Wasp processes. 2. Delete the Docker volume associated with your Wasp database. The volume name typically follows the pattern wasp-dev-db-<project-name>-<hash>. 3. Run wasp start db again to create a fresh database. 4. Run wasp db migrate-dev to apply all migrations. 5. Finally, run wasp start to start your app. If you're still experiencing issues, it might be helpful to check the contents of your database to ensure all necessary tables are created. You can do this by connecting to the database directly, as described in this Discord thread (https://discord.com/channels/686873244791210014/1217295340785635418). Remember, when you delete and recreate the Docker image, you're essentially starting with a fresh database, so it's crucial to reapply all migrations to set up the correct schema. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @prof_mark, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
prof_mark
prof_markOP2mo ago
ah thank you kapa, i needed to run migrate-dev.
Want results from more Discord servers?
Add your server