Portainer Templates logo

Portainer Templates

drawDB drawDB

Container

DatabaseDevelopmentTools

Database diagram editor for drawing entity relationships in the browser, then exporting them as SQL for MySQL, PostgreSQL, SQLite, MariaDB or SQL Server, or importing an existing schema to see it. Source: https://github.com/drawdb-io/drawdb

Image details

Architecture: amd64, arm64
Image size: 29 MB
User: drawdb-io

Source details

Repo: drawdb-io/drawdb
Stars: 40.1k
Forks: 3k
Language: JavaScript
License: AGPL-3.0
Updated: 2 days ago
Website: drawdb.app/

Configuration

Type
Container
Platform
linux
Image
ghcr.io/drawdb-io/drawdb:latest
Ports
8098:80/tcp
Restart
unless-stopped

Template by NotAFlightRisk

Report issue

Notes

Open http://<your-host>:8098/editor. There's no login and nothing to back up on the server, since diagrams are saved in your browser's own storage, so another browser or a cleared cache starts empty. File --> Export as --> JSON keeps a copy, and File --> Import from brings it back. Plain /editor makes a fresh copy of your last diagram on every visit, so bookmark the /editor/diagrams/... address it moves you to. Share and version history need drawDB's separate backend, which isn't included. Icon fonts load from jsDelivr and cdnjs, and the home page at / pulls in tweets and a GitHub star count from outside services. Docs: drawdb-io.github.io/docs

Standalone Install

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

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 drawDB, 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 drawdb-io/drawdb for app-specific guidance.

<img width="64" alt="drawDB logo" src="https://raw.githubusercontent.com/drawdb-io/drawdb/HEAD/src/assets/icon-dark.png">
<h1>drawDB</h1>

Free, simple, and intuitive database schema editor and SQL generator.


<a href="https://drawdb.app/" style="display: flex; align-items: center;">
    <img src="https://img.shields.io/badge/Start%20building-grey" alt="drawDB"/>
</a>
<a href="https://discord.gg/BrjZgNrmR6" style="display: flex; align-items: center;">
    <img src="https://img.shields.io/discord/1196658537208758412.svg?label=Join%20the%20Discord&logo=discord" alt="Discord"/>
</a>
<a href="https://x.com/drawDB_" style="display: flex; align-items: center;">
    <img src="https://img.shields.io/badge/Follow%20us%20on%20X-blue?logo=X" alt="Follow us on X"/>
</a>

drawDB screenshot demo


DrawDB is a robust and user-friendly database entity relationship diagram (ERD) editor right in your browser. Build diagrams with a few clicks, export and import SQL scripts, generate migrations, customize your editor, and more without creating an account. See the full set of features on here.

Getting Started

Local Development

git clone https://github.com/drawdb-io/drawdb
cd drawdb
npm install
npm run dev

Build

git clone https://github.com/drawdb-io/drawdb
cd drawdb
npm install
npm run build

Docker Build

docker build -t drawdb .
docker run -p 3000:80 drawdb

If you want to enable sharing, set up the server and environment variables according to .env.sample. This is optional unless you need to share files.
With the Docker image, pass the server URL when starting the container. No rebuild is needed:
docker run -p 3000:80 -e VITE_BACKEND_URL=https://your-drawdb-server.example.com ghcr.io/drawdb-io/drawdb:latest

Contributing

Please see CONTRIBUTING.md for guidelines on how to contribute to this project.

Support

Serve drawDB 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 drawdb.example.com to http://drawdb:80

Add this to your Caddyfile

drawdb.example.com {
	reverse_proxy http://drawdb: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 drawdb
  • 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:8098 failed: port is already allocated", something else on your server is using that port.

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

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/drawdb-io/drawdb: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
  • 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 drawdb --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Data disappears when the container is recreated

This template doesn't define any volumes, so everything drawdb saves lives inside the container and is lost on update or recreate.

  • Add a volume mapping for drawdb's data folder before storing anything you care about.

Raise an issue

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

A single container

drawDB 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 drawDB needs bundled into one download. This template pulls ghcr.io/drawdb-io/drawdb:latest, which Docker fetches once (about 29 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. drawDB's comes from the GitHub Container Registry, published by drawdb-io.

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. 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, 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 8098:80 means it's reachable on port 8098 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:8098 in a browser. It opens:

  • 8098:80, likely the web interface

No stored data

This template doesn't mount any storage, so whatever drawDB writes stays inside the container and is wiped if it's recreated or updated. That's fine for something stateless, but add a volume before trusting it with anything you want to keep.

Restart policy

The restart policy here is unless-stopped, so Docker restarts drawDB 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 drawDB 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 drawdb. That's what you'll spot in the containers list and use in commands like docker logs drawdb.

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

drawDB is open source, released under the AGPL-3.0 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 drawDB up. Add the template list to Portainer once, then deploying drawDB is a click rather than a wall of config.