Our take
- Activity
- 35
- Community
- 52
- Issues
- 43
- Pull requests
- 43
+5 stars in the last 30 days
- Slower to close issues than 89% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
2,280Forks
461Change since Nov 16, 2026: +2 stars·0 forks
Overview
jgraph/docker-drawio packages the draw.io diagramming and whiteboarding application as a Docker image. It is intended for people and teams who want to host the editor themselves rather than rely on the hosted service, while keeping deployment and runtime configuration in a container.
The repository also includes Compose configurations for cloud-storage integrations and Nextcloud. Its image is based on Tomcat, can run behind a reverse proxy, and uses a dedicated non-root user by default.
Key Features
- Docker image kept up to date with draw.io releases.
- Tomcat-based deployment for direct access or use behind a reverse proxy.
- Compose configuration for Google Drive, Microsoft OneDrive, and GitLab integrations.
- Separate Compose setup for integration with Nextcloud.
- Startup configuration through environment variables, including editor settings and deployment URLs.
- Automatic self-signed or Let's Encrypt certificate setup, with support for a mounted SSL keystore.
- Runs as a dedicated non-root user by default, with guidance for arbitrary UIDs and OpenShift.
Use Cases
- Teams that need a self-hosted diagram editor under their own domain and infrastructure.
- Administrators deploying draw.io behind an existing reverse proxy or at a sub-path.
- Nextcloud operators who want to make diagram editing available within their installation.
- Organizations that need diagram access connected to Google Drive, OneDrive, or GitLab.
Getting Started
Run the image and open the local editor:
docker run -it --rm --name=draw -p 8080:8080 -p 8443:8443 jgraph/drawio
Then visit http://localhost:8080/?offline=1&https=0. See the README for Compose deployments, integrations, SSL, and configuration options.
Considerations
- The image serves the draw.io application; it does not include the separate export-server image, which this project says has reached end of life. Some server-rendered export options are therefore unavailable.
- Runtime configuration is written into the webapp at startup. A read-only root filesystem is not supported, and custom UIDs need to run with GID 0 for the entrypoint to apply configuration.
- The README describes
?offline=1as disabling cloud storage support. Enable integrations only when needed and configure their OAuth credentials and redirect URIs appropriately. - The project is licensed under GPL-3.0; software included in the image has its own license terms.
Found this useful?
Share it with someone who would like docker-drawio.