Default credentials not found in Cloud Run
I am writing a program that uses postgres dialect to talk to cloud spanner. My application is a gin server and I'm using pgadapter to connect as described in this document.
My application runs fine locally. But when I deploy it to the cloud to run, I receive the following log.
This error mainly comes from the startpgadapterwithcredentials
function.
func StartPGAdapter(ctx context.Context, project, instance string) (port int, cleanup func(), err error) { credentials, err := google.FindDefaultCredentials(ctx) fmt.Println("credentials " + (credentials.ProjectID) + "json " + utils.ToString(credentials.JSON) + "ts " + utils.ToString(credentials.TokenSource)) if err != nil { return 0, func() {}, err } return StartPGAdapterWithCredentials(ctx, project, instance, credentials) } func StartPGAdapterWithCredentials(ctx context.Context, project, instance string, credentials *google.Credentials) (port int, cleanup func(), err error) { if credentials == nil { return 0, func() {}, fmt.Errorf("credentials cannot be nil") } if credentials.JSON == nil || len(credentials.JSON) == 0 { return 0, func() {}, fmt.Errorf("only JSON based credentials are supported") } credentialsFile, err := os.CreateTemp(os.TempDir(), "pgadapter-credentials") if err != nil { return 0, func() {}, err }
On my local system, google_application_credentials
is set up so it is able to get the credentials. However, this does not work when running in the cloud.
How to make it run in cloud run?
Additional information: Follow the examples provided here.
Correct Answer
It looks like you are trying to start the PGAdapter in an embedded container on Cloud Run and then copy the service account credentials from your environment to the PGAdapter Embedded container. The problem is that Cloud Run does not provide access to the underlying service account files. Instead, you should let the Google Cloud library obtain the environment's default credentials.
The difficult part in your example is that you are starting the PGAdapter in an embedded container, which means there are no default credentials in that environment. The recommended way to run a PGAdapter on Cloud Run is to include it in the main container. This will enable the PGAdapter to obtain only the default credentials provided by Cloud Run. This means that you should not specify the -c /path/to/credentials.json
parameter when starting the PGAdapter.
There are (at least) two ways to include a PGAdapter in the main container:
- Add the Java
.jar
file build to your Docker image and start the PGAdapter in the container. See [this example] to learn how to start a PGAdapter directly from a.jar
file. This also requires you to add the Java JRE to the Docker image. - Let your Docker build extend the PGAdapter base Docker image. This will automatically include all dependencies required by the PGAdapter. You must override the
ENTRYPOINT
of the base image.
See Go's PGAdapter Cloud Run Example for an extensive (runnable) example of the latter option.
The above is the detailed content of Default credentials not found in Cloud Run. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
