percona / percona/pg_oidc_validator

`pg-oidc-validator-pgdg18` is not arm64 compatible

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
36
Forks
15
PR merge metrics
No merged PRs in 30d

Description

I added 127.0.0.1 keycloak to my /etc/hosts file on my Mac with Apple chip & then executed the following commands.

docker compose up -d
docker compose run --rm psql-client

Then I'm seeing following error.

========================================
PostgreSQL OAuth Client
========================================

Connecting to PostgreSQL with OAuth...

When prompted, follow the device flow:
  1. Visit the URL shown in your browser
  2. Enter the device code
  3. Login with: testuser / asdfasdf

========================================

psql: error: connection to server at "postgres" (172.24.0.3), port 5432 failed: FATAL:  could not access file "pg_oidc_validator": No such file or directory

The root cause is that pg-oidc-validator-pgdg18 is not arm64 compatible.

dpkg: error processing archive pg-oidc-validator-pgdg18.deb (--install):

 package architecture (amd64) does not match system (arm64)

Errors were encountered while processing:

 pg-oidc-validator-pgdg18.deb

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.

Research direction

Reproduce the failure on an Apple-chip Mac with docker compose up -d and docker compose run --rm psql-client, then inspect how pg-oidc-validator-pgdg18.deb is installed in the container. Done means the package is usable on arm64 and the PostgreSQL OAuth client connects successfully without the missing-file error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, postgresql
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.