Hacker News Reader

Curious. I run the docker image all the time and haven't had any issues with the port binding. What kind of system are you using? and what was your launch command?

You can double check that we are exposing port 3000 from the container which is where the app is designed to run by default. The Dockerfile used to build the image is in our repo here: https://github.com/metabase/metabase/blob/master/bin/release...

Heroku sometimes times out if the application takes too long to start. Could you try again and see if it works? We're working on making Heroku deploys more robust.

It seems that the Docker issue is memory overflow in container. I tried to run the docker image in a 512mb Digitalocean droplet that already runs several processes that also consume memory so I think it's expected considering Metabase runs on JVM.

Are you on virtualbox? Sounds like a port binding issue. If you open an issue at github.com/metabase/metabase or http://discourse.metabase.com/ we'll try to debug exactly what's happening.

Same here, tried deploying with the Heroku button but can't access the app after deployment.