To create a self-hosted analytics dashboard with Metabase and Docker, deploy the Metabase container, store its application data in PostgreSQL, connect your business database, and build dashboards from saved questions and visualizations. This setup gives you a private business intelligence environment where you control the server, database connections, users, permissions, and reporting workflow.<\/p>
Metabase works well for self-hosted analytics because it combines a visual query builder, SQL editor, dashboard filters, scheduled reports, and team permissions in one interface. Docker makes the deployment portable, while PostgreSQL keeps Metabase data such as users, dashboards, saved questions, and settings outside the container.<\/p>
The fastest setup is to run the official Metabase Docker image and open the setup wizard on port 3000. For long-term reporting, use Docker Compose with PostgreSQL or deploy the Metabase Docker template on Hostinger VPS to reduce manual configuration.<\/p>
Before installing Metabase with Docker, set up the basic private server,<\/a> database, and access details needed to run the container and complete the setup wizard.<\/p> You need:<\/p> The PostgreSQL application database is different from the business database you connect to analytics. PostgreSQL stores Metabase’s own settings and saved assets, while the connected business database provides the data used to create charts, reports, and dashboards.<\/p> You can install Metabase with Docker by pulling the official Metabase image, running it as a container, and opening the setup wizard in your browser. This method is best for testing Metabase or creating a basic self-hosted analytics dashboard before moving to a production setup.<\/p> Before starting, make sure Docker is installed on your server<\/a> or local machine. You also need access to the terminal and an available port, such as 3000, for the Metabase web interface.<\/p> First, download the official Metabase image from Docker Hub:<\/p> This command downloads the latest open-source Metabase Docker image to your server. Docker uses this image to create and run the Metabase container.<\/p> After downloading the image, start Metabase with this command:<\/p> Here is what each part of the command does:<\/p> Metabase starts on port 3000 by default. If another application already uses this port, map Metabase to a different host port:<\/p> With this command, Metabase still uses port 3000 inside the container, but you access it through port 3001 on your server.<\/p> To confirm that the container started correctly, list your running Docker containers:<\/p> You should see a container named metabase in the output.<\/p> You can also check the Metabase logs:<\/p> Wait until the logs show that Metabase has finished starting. The first launch can take a few minutes because Metabase initializes its application files.<\/p> Once the container is running, open Metabase in your browser.<\/p> If you installed Metabase on a local machine, go to:<\/p> If you installed Metabase on a VPS, use your server IP address:<\/p> Replace your-server-ip with the actual IP address of your VPS.<\/p> The Metabase setup wizard will ask you to create an admin account, choose your language, and connect your first data source. After completing the setup, you can start creating questions, charts, and dashboards from your business data.<\/p> To stop Metabase, run:<\/p> To start it again, run:<\/p> To restart Metabase after a configuration change, use:<\/p> This basic Docker setup is useful for testing Metabase, but it is not the best option for production. By default, Metabase uses an embedded application database inside the container. For a long-term business intelligence dashboard, run Metabase with PostgreSQL and Docker Compose so your dashboards, users, settings, and saved questions remain stored safely outside the container.<\/p> The basic Docker installation works for testing, but a production Metabase setup should use PostgreSQL as the application database. PostgreSQL stores your Metabase users, dashboards, saved questions, settings, and permissions outside the Metabase container, so your analytics workspace remains intact when you update, recreate, or restart the container.<\/p> Docker Compose<\/a> lets you run Metabase and PostgreSQL together from one configuration file. This makes the setup easier to manage than manually starting each container.<\/p> First, create a separate directory for your Metabase deployment:<\/p> This directory will store your Docker Compose configuration file.<\/p> Create a new docker-compose.yml file:<\/p> Then, add the following configuration:<\/p> Replace change_this_password with a strong password before starting the containers. Use the same password for POSTGRES_PASSWORD and MB_DB_PASS, as Metabase uses it to connect to the PostgreSQL database.<\/p> Run the following command from the same directory as your docker-compose.yml file:<\/p> Docker Compose will download the required images, create the PostgreSQL database container, and start the Metabase container in the background.<\/p> To check if both containers are running, use:<\/p> You should see two services: postgres and metabase.<\/p> Metabase can take a few minutes to start during the first launch. Check the logs with:<\/p> Wait until the logs show that Metabase has finished initializing. If Metabase cannot connect to PostgreSQL, ensure the database name, username, password, port, and host match across both service configurations.<\/p> After the containers are running, open Metabase in your browser:<\/p> Replace your-server-ip with your VPS IP address. If you are running the setup locally, use:<\/p> The setup wizard will ask you to create an admin account and configure your first data source. This data source is separate from the PostgreSQL application database used by Metabase itself.<\/p> Use these commands to manage your Metabase deployment:<\/p> This stops the Metabase and PostgreSQL containers.<\/p> This starts the containers again.<\/p> This restarts both services.<\/p> This stops and removes the containers, but keeps the PostgreSQL volume unless you explicitly remove volumes.<\/p> Avoid running docker compose down -v unless you want to delete the PostgreSQL volume. That volume contains your Metabase application data, including dashboards, saved questions, users, and settings.<\/p> To update Metabase, pull the latest image and recreate the container:<\/p> Docker Compose replaces the Metabase container with a new one using the updated image. Your application data remains stored in the PostgreSQL volume.<\/p> Before updating a production Metabase instance, back up your PostgreSQL database. This protects your dashboards, saved questions, permissions, and configuration if the update fails or introduces compatibility issues.<\/p>\n
How to install Metabase with Docker<\/h2>
1. Pull the official Metabase Docker image<\/h3>
docker pull metabase\/metabase:latest<\/pre>
2. Run the Metabase container<\/h3>
docker run -d -p 3000:3000 --name metabase metabase\/metabase<\/pre>
\n
docker run -d -p 3001:3000 --name metabase metabase\/metabase<\/pre>
3. Check if the Metabase container is running<\/h3>
docker ps<\/pre>
docker logs -f metabase<\/pre>
4. Open the Metabase setup wizard<\/h3>
http:\/\/localhost:3000<\/pre>
http:\/\/your-server-ip:3000<\/pre>
5. Stop or restart the Metabase container<\/h3>
docker stop metabase<\/pre>
docker start metabase<\/pre>
docker restart metabase<\/pre>
How to run Metabase with Docker Compose and PostgreSQL<\/h2>
1. Create a project directory<\/h3>
mkdir metabase-docker\ncd metabase-docker<\/pre>
2. Create a Docker Compose file<\/h3>
nano docker-compose.yml<\/pre>
services:\npostgres:\nimage: postgres:16\ncontainer_name: metabase-postgres\nrestart: unless-stopped\nenvironment:\nPOSTGRES_DB: metabase\nPOSTGRES_USER: metabase\nPOSTGRES_PASSWORD: change_this_password\nvolumes:\n- metabase-postgres-data:\/var\/lib\/postgresql\/data\nmetabase:\nimage: metabase\/metabase:latest\ncontainer_name: metabase\nrestart: unless-stopped\nports:\n- \"3000:3000\"\nenvironment:\nMB_DB_TYPE: postgres\nMB_DB_DBNAME: metabase\nMB_DB_PORT: 5432\nMB_DB_USER: metabase\nMB_DB_PASS: change_this_password\nMB_DB_HOST: postgres\ndepends_on:\n- postgres\nvolumes:\nmetabase-postgres-data:<\/pre>
3. Start Metabase and PostgreSQL<\/h3>
docker compose up -d<\/pre>
docker compose ps<\/pre>
4. Check the Metabase logs<\/h3>
docker compose logs -f metabase<\/pre>
5. Open Metabase in your browser<\/h3>
http:\/\/your-server-ip:3000<\/pre>
http:\/\/localhost:3000<\/pre>
6. Manage the Docker Compose deployment<\/h3>
docker compose stop<\/pre>
docker compose start<\/pre>
docker compose restart<\/pre>
docker compose down<\/pre>
7. Update Metabase with Docker Compose<\/h3>
docker compose pull metabase\ndocker compose up -d metabase<\/pre>
How to deploy Metabase faster with Hostinger VPS<\/h2>