Portainer Templates logo

Portainer Templates

Dashy (container) Dashy (container)

DashboardTools

The ultimate personal dashboard, keep all your self-hosted services and websites organized. Includes live status monitoring, widgets, icons, themes, 30+ languages, instant search, multi-page support, UI editor, authentication and more. GitHub: lissy93/dashy

Image details

Pulls: 18.7M
Architecture: amd64, arm64, arm/v7
Image size: 111 MB
Latest: 4.5
User: lissy93
Created: May 22, 2021
Updated: 14 hours ago
Status: active

Source details

Repo: lissy93/dashy
Stars: 26.2k
Forks: 2k
Language: Vue
License: MIT
Latest: 4.5.0 · 20 days ago
Updated: 14 hours ago
Website: dashy.to/

Configuration

Type
Container
Platform
linux
Image
lissy93/dashy:latest
Ports
4000:8080/tcp
Volumes
/app/user-data
Env vars
NODE_ENV=productionTZ=UTC
Restart
unless-stopped

Notes

Dashy's main config lives in `/app/user-data/conf.yml`. You can put additional configs, styles, icons, CSS, and other resources in this `user-data` directory too. See the docs at https://dashy.to/docs for more info.

Standalone Install

Select an install method, to see config/commands for deploying Dashy (container)

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 Dashy (container), fill in any config options, and hit Deploy

Template Import URL

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

More install options in our documentation, or see lissy93/dashy for app-specific guidance.

Dashy

Dashy helps you organize your self-hosted services by making them accessible from a single place

<br/>

User Showcase | Live Demo | Getting Started | Documentation | GitHub

Serve Dashy (container) 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 dashy-container.example.com to http://dashy:8080

Add this to your Caddyfile

dashy-container.example.com {
	reverse_proxy http://dashy:8080
}

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 dashy
  • 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:4000 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :4000
  • Stop the other service, or pick a different host port. In 4000:8080 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:4000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, dashy can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 4000

Image won't pull

Test the pull directly on the host: docker pull lissy93/dashy:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "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.

  • This image supports: amd64, arm64, arm/v7
  • 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 unless-stopped 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 dashy --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

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

A single container

Dashy (container) runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Dashy (container) needs bundled into one download. This template pulls lissy93/dashy:latest, which Docker fetches once (about 111 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Dashy (container)'s comes from Docker Hub, published by lissy93.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 4.5. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 4000:8080 means it's reachable on port 4000 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:4000 in a browser. It opens:

  • 4000:8080, likely the web interface

Volumes

A volume is where Dashy (container) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/user-data as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Dashy (container) takes 2 of them, all with defaults you can leave alone or tweak:

  • NODE_ENV, defaults to production. Node environment
  • TZ, defaults to UTC. Timezone, e.g. Europe/London (used for logs and time widgets)

Restart policy

The restart policy here is unless-stopped, so Docker restarts Dashy (container) after a crash or reboot, but leaves it off when you stop it on purpose. 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

Nothing custom is set, so Dashy (container) sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container dashy. That's what you'll spot in the containers list and use in commands like docker logs dashy.

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.

Open source license

Dashy (container) is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

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