Docker image V0.29.3 [SOLVED]

redbeard · August 9, 2018, 5:08pm

Hi,

My installation of Metabase on Azure was set up and using v0.29.3. It has now just updated to the new docker image v0.30.0. This version doesn’t seem to be working for me, and a bug has been raised.

I was wondering whether anyone has a docker image of v0.29.3 they could share with me, or explain how I can take the source code of v0.29.3 from: https://github.com/metabase/metabase/releases and turn this into a docker image of v0.29.3 which I am hoping will work until the bug is fixed.

I have installed docker, I don’t think I’m using it correctly!
(on a Windows machine) I open powershell >> go to the directory containing the unzipped source code >> type: docker build -t metabase

Many thanks for any help

jornh · August 9, 2018, 5:59pm

So docker has this thing called tags - so if you specify that you get an exact image from here, and you have turned back the clock to almost anywhere ind the past yo want to go: https://hub.docker.com/r/metabase/metabase/tags/

so in your case docker pull metabase/metabase:v0.29.3 or something, and you have it. As you probably already guessed :latest is a specially named default tag it runs with if you don’t specify a tag.

Read up a but on docker pull and docker run in Docker’s documentation and you’re good for now.

It’s BTW always a best practice to “pin” to a specific tag in your configuration - so your have a predictable environment.

Hope that gives you what you need?

maz · August 9, 2018, 6:42pm

This version doesn’t seem to be working for me, and a bug has been raised.

@redbeard It looks like this is the issue you're referencing (I saw you commented on it). As you already wrote there, posting some logs and any other additional details you have would be very helpful. Thanks.

github.com/metabase/metabase

App fails on w/postgresql after migrating to 0.30

opened 07:17AM - 09 Aug 18 UTC

closed 04:56AM - 05 Aug 19 UTC

pfeiffer

Type:Bug Priority:P1 Operation/Heroku

After upgrading to 0.30 I'm seeing this error in console on Heroku: ``` Aug …09, 2018 6:50:02 AM org.postgresql.core.v3.ConnectionFactoryImpl log WARNING: SQLException occurred while connecting to ec2-54-76-233-110.eu-west-1.compute.amazonaws.com:5432 org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "...", user "...", database "....", SSL off ``` I've checked and `MB_DB_CONNECTION_URI` **does** contain the `?sslmode=require..` string by adding this to the startup script: `echo "Using this MB_DB_CONNECTION_URI: ${MB_DB_CONNECTION_URI}"` Running the migrations tool manually, I get the following output (notice the **SSL off** in last line): ``` 08-09 06:49:21 INFO metabase.util :: Loading Metabase... 08-09 06:49:31 INFO util.encryption :: Saved credentials encryption is ENABLED for this Metabase instance. 🔐 For more information, see https://www.metabase.com/docs/latest/operations-guide/start.html#encrypting-your-database-connection-details-at-rest 08-09 06:49:42 INFO metabase.core :: Starting Metabase in STANDALONE mode 08-09 06:49:42 INFO metabase.core :: Launching Embedded Jetty Webserver with config: {:port 44749} 08-09 06:49:42 INFO metabase.core :: Starting Metabase version v0.30.0 (04836dc release-0.30.0) ... 08-09 06:49:42 INFO metabase.core :: System timezone is 'GMT' ... WARNING: any? already refers to: #'clojure.core/any? in namespace: monger.collection, being replaced by: #'monger.collection/any? 08-09 06:49:45 INFO metabase.core :: Setting up and migrating Metabase DB. Please sit tight, this may take a minute... 08-09 06:49:45 INFO metabase.db :: Verifying postgres Database Connection ... 08-09 06:49:48 INFO metabase.db :: Verify Database Connection ... ✅ 08-09 06:49:48 INFO metabase.db :: Running Database Migrations... 08-09 06:49:48 INFO metabase.db :: Setting up Liquibase... 08-09 06:49:48 INFO metabase.db :: Liquibase is ready. 08-09 06:49:48 INFO metabase.db :: Checking if Database has unrun migrations... 08-09 06:50:01 INFO metabase.db :: Database Migrations Current ... ✅ com.mchange.v2.cfg.DelayedLogItem [ level -> FINE, text -> "The configuration file for resource identifier 'hocon:/reference,/application,/c3p0,/' could not be found. Skipping.", exception -> null] 08-09 06:50:01 INFO db.migrations :: Running all necessary data migrations, this may take a minute. 08-09 06:50:02 INFO db.migrations :: Finished running data migrations. 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.notifications 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.metabot-lifecycle 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.dependencies 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.activity-feed 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.last-login 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.revision 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.sync-database 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.view-log 👂 08-09 06:50:02 INFO metabase.events :: Starting events listener: metabase.events.driver-notifications 👂 Aug 09, 2018 6:50:02 AM org.postgresql.core.v3.ConnectionFactoryImpl log WARNING: SQLException occurred while connecting to .... org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "...", user "....", database "...", SSL off ```

redbeard · August 10, 2018, 9:36am

Thanks @jornh - that has brought the version back to v0.29.3. I will now be ‘pinning’ my versions - I didn’t know that was a thing!

V0.29.3 came back ok - but all questions/settings/dashboards have disappeared. I’m guessing this is because v0.30 had some database migrations? I’ve rolled my PostgreSQL application db back to one from before the update. This seems to work.

Thanks again

redbeard · August 10, 2018, 9:37am

Thanks @maz - I’ve added a bit more info

jornh · August 10, 2018, 9:49am

Exactly!

Sounds like the title in the first post can be marked with [SOLVED] (you can do that yourself)

Side note: @maz - nudge nudge - I mentioned the Discourse solved plugin before - would be a nice addition. Would help with discoverability/usability and (you can consider a nice communty site to be part of your marketing "budget" as well)