Skip to content
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

Temporal container errors #441

Closed
Zibbp opened this issue May 31, 2024 · 2 comments
Closed

Temporal container errors #441

Zibbp opened this issue May 31, 2024 · 2 comments

Comments

@Zibbp
Copy link
Owner

Zibbp commented May 31, 2024

If you are reading this you need to perform the below instructions!

If your ganymede-temporal container has recently updated (pulling in the newest temporal image) you will encounter errors when starting the container. If To resolve this follow these instructions.

  1. Ensure an archive is not active
  2. Bring down the temporal container docker compose down ganymede-temporal
  3. Perform these modifications to the compose file
  ganymede-temporal:
-   image: temporalio/auto-setup:1
+   image: temporalio/auto-setup:1.23
    container_name: ganymede-temporal
    depends_on:
      - ganymede-db
    environment:
-     - DB=postgresql # this tells temporal to use postgres (not the db name)
+     - DB=postgres12 # this tells temporal to use postgres (not the db name)
      - DB_PORT=5432
      - POSTGRES_USER=ganymede
      - POSTGRES_PWD=PASSWORD
  1. Pull the image docker compose pull ganymede-temporal
  2. Bring temporal up docker compose up -d ganymede-temporal
@ccKep
Copy link

ccKep commented Jun 2, 2024

For some reason using DB=postgres12 did not work for me:
config validation error: persistence config: missing config for datastore "default".

  • I made sure I am on 1.23 (even tried 1.22)
  • I tried dropping the temporal and temporal_visibility databases from postgres to ensure a clean slate

After switching back to DB=postgres (using 1.23 of temporalio/auto-setup) it started working again.

@c-hri-s
Copy link

c-hri-s commented Jun 7, 2024

CHanges worked fine for me (DB=postgres12) - thanks

@Zibbp Zibbp unpinned this issue Jul 28, 2024
@Zibbp Zibbp closed this as completed Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@ccKep @c-hri-s @Zibbp and others