Thursday, November 11, 2021

[google-cloud-sql-discuss] Re: Cloud SQL Proxy invalid json coming from Docker Compose

For what it's worth in the cloud_sql_proxy command in the first container I do include the file name "credentials.json" just forget to include it here

On Thursday, November 11, 2021 at 11:42:37 AM UTC-5 Justis Gipson wrote:
Learning as I go here, but ran into an issue running the cloud_sql_proxy from a compose file.

`cloudsql-proxy    | 2021/11/11 15:57:39 invalid json file "app/secrets/cloudsql/credentials.json": open app/secrets/cloudsql/credentials.json: no such file or directory`

The error is only occurring when ran from in the docker-compose file. When I run it locally it works as expected.

I have a feeling it's how the volumes are mounted, but I am not sure at this point.

I've tried everything I have read in the docs, GCP Slack community & StackOverflow - nothing has helped.

Here's my compose:

version: '3'

services:
# Gonna have to figure this out...
#
cloudsql-proxy:
container_name: cloudsql-proxy
env_file:
- ./.dev.env
restart: always
volumes:
- credentials:/app
ports:
- 5432:5432
command: /cloud_sql_proxy -credential_file=app/secrets/cloudsql/ -instances=XXPROJECT_IDXX:XXREGIONXX:XXDB_NAMEXX=tcp:0.0.0.0:5432 &
# depends_on:
# - feathers

feathers:
build:
context: .
dockerfile: dockerfile
restart: always
working_dir: /app
volumes:
- ./:/app
- node_modules_cache:/app/node_modules/
ports:
- 3030:3030
env_file:
- ./.dev.env
command: 'npm run dev'
depends_on:
- cloudsql-proxy

volumes:
credentials:
node_modules_cache:


Any insight into why the compose file is telling me the json is invalid would be helpful.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/f85e32c5-6e72-4521-a595-e362681e590bn%40googlegroups.com.

No comments:

Post a Comment