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

(psycopg2.OperationalError) SCRAM authentication requires libpq version 10 or above #1

Open
burakince opened this issue Jul 10, 2022 · 3 comments · Fixed by pbrit/mlflow#1

Comments

@burakince
Copy link
Owner

Describe the bug

When we try to use mlflow docker image on arm64 architecture with Postgres connection, the driver returns the following error.

(psycopg2.OperationalError) SCRAM authentication requires libpq version 10 or above

To Reproduce

Steps to reproduce the behavior:

  1. Run the image on arm64 machine with PostgreSQL connection settings.
  2. Look up to starting logs
  3. See error

Expected behavior

It must start to connect PostgreSQL database.

** Tested system:**

  • Architecture: arm64 (Raspberry Pi)
  • Cluster: Kubernetes 1.23.5
  • Mlflow Docker Image Version: 1.27.0.9

Additional context

You can find more information from this issue.

@burakince
Copy link
Owner Author

burakince commented Jul 10, 2022

THe solution looks like usage of psycopg3 driver. But latest version of sqlalchemy (1.4.39) doesn't not support psycopg dialect. It's part of the milestone 2.0 for the sqlalchemy.

@ecederstrand
Copy link

@burakince I stumbled into this issue today. Is there a workaround? The linux/arm64 images at https://hub.docker.com/r/burakince/mlflow/tags don't seem to work for me either.

@burakince
Copy link
Owner Author

Hi @ecederstrand ,

Sorry for the late response. You can use Mysql for your DB backend. It works fine on the arm64 arch. Unfortunately, I don't know any other workaround for this issue. :(

Best,
Burak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants