METABASE GCP HOW TO

Select you Cloud SQL Connection (it should match your startup.sh instance name)Īfter deploy if you watch your logs it keeps restarting over and over and the metabase login screen never appears, it keeps saying polishing tables and things like that. JAVA_OPTS = ‘-Xmx2048m’ <- without the quotes but with the dash at the beginning, this is to allow the container to use almost all the 1GB of memory instead of only 400Mb as default. MB_DB_TYPE = in my case ‘postgres’ without the quotes I edited the Dockerfile and added the cloud sql instance name (This can be found on your SQL instance overview) as mentions.Īfter deployed/pushed the image to Google Container Registry I just went and created a new Google Cloud Run service.Īdded 2GB of memory but noticed that 1GB is also fine, selected my image (that I already pushed to Container Registry) I still had to use a symlink because even socat can’t handle paths that contain. Nohup socat -d -d TCP4-LISTEN:5432,fork UNIX-CONNECT:pg.sock &

# Forward TCP:5432 to Cloud SQL Unix socket RUN ln -s /cloudsql//.s.PGSQL.5432 pg.sock # Set up symlink to Cloud SQL UNIX socket I made my own Dockerfile like this: FROM metabase/metabase …but maybe you could do a workaround with a TCP forward

METABASE GCP HOW TO

That looks like you can make a string like think this works if you’ve included the relevant Google Cloud libraries in the jar itself, but I don’t know how to do that. I set MB_DB_CONNECTION_URL to but Metabase seems to ignore this and reverts to H2 without throwing any exceptions.

Metabase gcp