Portainer Templates logo

Portainer Templates

Freeboard Freeboard

Stack

DashboardIOT

Freeboard is a turn-key HTML-based 'engine' for dashboards. Besides a nice looking layout engine, it provides a plugin architecture for creating datasources (which fetch data) and widgets (which display data)— freeboard then does all the work to connect the two together.

Configuration

Type
Compose
Platform
linux
Ports
8000:80/tcp
Restart
always
Source
Repo

Template by xneo1·Source

Services

nginx

Configuration

Image
nginx:1.13
Ports
8003:80

Image details

Pulls: 13.3B
User: stackbrew
Created: Jun 05, 2014
Updated: 4 days ago
Status: active

freeboard

Configuration

Image
freeboard
Build
.

Standalone Install

Select an install method, to see config/commands for deploying Freeboard

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Freeboard, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
    nginx:
        image: nginx:1.13
        ports:
            - "8003:80"
        volumes_from:
            - freeboard:ro
    freeboard:
        image: freeboard
        build: .

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/freeboard.yml up -d

More install options in our documentation.

Container Documentation

nginx Documentation

Official build of Nginx.

Serve Freeboard on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying freeboard.example.com to http://nginx:80

Add this to your Caddyfile

freeboard.example.com {
	reverse_proxy http://nginx:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8003 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8003
  • Stop the other service, or pick a different host port. In 8003:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8003. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, freeboard can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8003

Image won't pull

Test the pull directly on the host: docker pull nginx:1.13

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The always restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Freeboard is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • nginx runs nginx:1.13
  • freeboard runs freeboard

Ports

A port is the door the app answers on. A mapping like 8003:80 means it's reachable on port 8003 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8003 in a browser. It opens:

  • 8003:80, likely the web interface

Restart policy

The restart policy here is always, so Docker brings Freeboard back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like nginx) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Freeboard up. Add the template list to Portainer once, then deploying Freeboard is a click rather than a wall of config.