Deploying on Google Cloud Run #748

benwa · 2025-04-30T14:12:55Z

benwa
Apr 30, 2025

I am a beginner in containers, so please put on the kid gloves.

I am attempting to use Google Cloud Run to deploy Ganymede. The frontend runs as expected, but it seems that no environment variables are being passed to the container.

I keep seeing the following error in the log:

anic: error getting config

goroutine 1 [running]:
github.com/rs/zerolog/log.Panic.(*Logger).Panic.func1({0x18339fc?, 0x0?})
	/go/pkg/mod/github.com/rs/zerolog@v1.34.0/log.go:405 +0x27
github.com/rs/zerolog.(*Event).msg(0xc0004893b0, {0x18339fc, 0x14})
	/go/pkg/mod/github.com/rs/zerolog@v1.34.0/event.go:158 +0x2aa
github.com/rs/zerolog.(*Event).Msg(...)
	/go/pkg/mod/github.com/rs/zerolog@v1.34.0/event.go:110
github.com/zibbp/ganymede/internal/server.SetupApplication({0x29c2a50, 0x35a8c80})
	/app/internal/server/server.go:64 +0x105
github.com/zibbp/ganymede/internal/server.Run({0x29c2a50, 0x35a8c80})
	/app/internal/server/server.go:183 +0x32
main.main()
	/app/cmd/server/main.go:23 +0x1f8

My scrubbed YAML:

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  ...
spec:
  template:
    ...
    spec:
      ...
      containers:
      - name: ganymede-1
        image: REDACTED
        ports:
        - name: http1
          containerPort: 8080
        env:
        - name: DB_HOST
          value: REDACTED
        - name: DB_PORT
          value: '5432'
        - name: DB_USER
          value: REDACTED
        - name: DB_NAME
          value: REDACTED
        - name: TZ
          value: America/New_York
        - name: SHOW_LOCALE_BUTTON
          value: 'false'
        - name: TWITCH_CLIENT_ID
          value: REDACTED
        - name: DB_PASS
          valueFrom:
            secretKeyRef:
              key: latest
              name: DB_PASS
        - name: TWITCH_CLIENT_SECRET
          valueFrom:
            secretKeyRef:
              key: latest
              name: TWITCH_CLIENT_SECRET
        resources:
          ...
        volumeMounts:
        - name: ganymede-db-ssl
          mountPath: /data/db-ssl
        - name: ganymede-logs
          mountPath: /data/logs
        - name: ganymede-config
          mountPath: /data/config
        - name: ganymede-videos
          mountPath: /data/videos
        - name: ganymede-temp
          mountPath: /data/temp
        livenessProbe:
          ...
        startupProbe:
          ...
      volumes:
      - name: ganymede-db-ssl
        csi:
          driver: gcsfuse.run.googleapis.com
          readOnly: true
          volumeAttributes:
            bucketName: ganymede-db-ssl
      - name: ganymede-logs
        csi:
          driver: gcsfuse.run.googleapis.com
          volumeAttributes:
            bucketName: ganymede-logs
      - name: ganymede-config
10000

        csi:
          driver: gcsfuse.run.googleapis.com
          volumeAttributes:
            bucketName: ganymede-config
      - name: ganymede-videos
        csi:
          driver: gcsfuse.run.googleapis.com
          volumeAttributes:
            bucketName: ganymede-videos
      - name: ganymede-temp
        emptyDir:
          medium: Memory
          sizeLimit: 32G
  traffic:
  ...
status:
  ...

Any ideas?

Zibbp · 2025-04-30T21:25:34Z

Zibbp
Apr 30, 2025
Maintainer

I've never used cloud run so I can't help much. Can you exec into the container and run env to print all ENV vars? Do you see your configured ones?

0 replies

benwa · 2025-05-01T13:21:36Z

benwa
May 1, 2025
Author

Not really sure what happened, but now it seems the environment variables are loaded. I wasn't able to exec into the container though, apparently you can't do that with Cloud Run.

Now I'm getting error running auto migration, which looks like it's an issue connecting to the database.
I am attempting to use Google's Cloud SQL with Postgres 14. I made a blank database and a user with permissions to it. Is that all that is required?

Edit:
Turns out if you use Cloud SQL with Cloud Run, it will by default use a Cloud SQL Auth Proxy which needs to be in a UNIX socket format for DB_HOST. I now see tables in the database!

Edit 2:
Now I'm just having trouble actually logging in.

{
    "message": "Request failed with status code 404",
    "name": "AxiosError",
    "stack": "AxiosError: Request failed with status code 404\n    at eC (https://archive.REDACTED.com/_next/static/chunks/5040-db83e699db00f794.js:12:43231)\n    at XMLHttpRequest.m (https://archive.REDACTED.com/_next/static/chunks/5040-db83e699db00f794.js:12:47690)\n    at tn.request (https://archive.REDACTED.com/_next/static/chunks/5040-db83e699db00f794.js:12:55792)\n    at async h (https://archive.REDACTED.com/_next/static/chunks/app/layout-07f9cd21f15bf9e0.js:1:334)\n    at async P (https://archive.REDACTED.com/_next/static/chunks/app/login/page-6ff4fee31605be85.js:1:3797)",
    "config": {
        "transitional": {
            "silentJSONParsing": true,
            "forcedJSONParsing": true,
            "clarifyTimeoutError": false
        },
        "adapter": [
            "xhr",
            "http",
            "fetch"
        ],
        "transformRequest": [
            null
        ],
        "transformResponse": [
            null
        ],
        "timeout": 0,
        "xsrfCookieName": "XSRF-TOKEN",
        "xsrfHeaderName": "X-XSRF-TOKEN",
        "maxContentLength": -1,
        "maxBodyLength": -1,
        "env": {},
        "headers": {
            "Accept": "application/json, text/plain, */*",
            "Content-Type": "application/json"
        },
        "withCredentials": true,
        "method": "post",
        "url": "/api/v1/auth/login",
        "data": "{\"username\":\"admin\",\"password\":\"ganymede\"}",
        "allowAbsoluteUrls": true
    },
    "code": "ERR_BAD_REQUEST",
    "status": 404
}

2 replies

Zibbp May 1, 2025
Maintainer

Interesting, is the API running? To test visit https://archive.REDACTED.com/health - it should return "OK".

Can also try logging in with curl:

curl -X POST --header "Content-Type: application/json" https://archive.REDACTED.com/api/v1/auth/login -d "{\"username\":\"admin\",\"password\":\"ganymede\"}"

Any concerning server logs?

benwa May 1, 2025
Author

/health gives me a 404. When I was attempting to get this working, I had set the container port to 4000, and was able to get an "OK" from /health.
The curl test just returns the main ganymede html.

The only server logs that I'm seeing are 404s for /health and /api/v1/auth/me. I don't see any logs at all in /data/logs.

Zibbp · 2025-05-01T23:12:39Z

Zibbp
May 1, 2025
Maintainer

The container port should be 4000, that is what the server runs on and what you should expose to your proxy. Not sure how that all works with Cloud Run but just know that 4000 is the HTTP server. If you restart the container you should see some logs on start up showing everything running

ganymede     | 2025-05-01 18:11:18,255 INFO success: api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ganymede     | 2025-05-01 18:11:18,255 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ganymede     | 2025-05-01 18:11:18,255 INFO success: worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2 replies

benwa May 1, 2025
Author

When I set it to 4000, I would get a port already used error. I tried to mimic the docker-compose by using 4800 and that error went away, the DB was seeded, the frontend loads, but then I get the login error.
I do see those three log entries on restart.

Zibbp May 2, 2025
Maintainer

I can't be much more help as I don't know Cloud Run. I recommend searching around to see if others have deployed similar apps on Cloud Run.
Port 4000 is the actual port, 4800 is the one mapped to 4000 in the container. Again I don't know if Cloud Run can use a mapped port like this or wants the real port.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Deploying on Google Cloud Run #748

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Deploying on Google Cloud Run #748

Uh oh!

benwa Apr 30, 2025

Replies: 3 comments · 4 replies

Uh oh!

Zibbp Apr 30, 2025 Maintainer

Uh oh!

Uh oh!

benwa May 1, 2025 Author

Uh oh!

Zibbp May 1, 2025 Maintainer

Uh oh!

benwa May 1, 2025 Author

Uh oh!

Zibbp May 1, 2025 Maintainer

Uh oh!

benwa May 1, 2025 Author

Uh oh!

Uh oh!

Zibbp May 2, 2025 Maintainer

benwa
Apr 30, 2025

Replies: 3 comments 4 replies

Zibbp
Apr 30, 2025
Maintainer

benwa
May 1, 2025
Author

Zibbp May 1, 2025
Maintainer

benwa May 1, 2025
Author

Zibbp
May 1, 2025
Maintainer

benwa May 1, 2025
Author

Zibbp May 2, 2025
Maintainer