![DocuSeal]()
DocuSeal
Open source DocuSign alternative for document filling and signing
Image details
Configuration
TypeContainerlinuxdocuseal/docuseal:latest3000:3000/tcp/dataunless-stoppedInstallation
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select the app you wish to deploy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
docker run -d --name docuseal \
-p 3000:3000/tcp \
-v /data \
--restart=unless-stopped \
docuseal/docuseal:latest
Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.
services:
docuseal:
image: docuseal/docuseal:latest
ports:
- 3000:3000/tcp
volumes:
- /data
restart: unless-stopped
Save this file as docuseal-stack.yml, then from a manager node, run docker stack deploy -c docuseal-stack.yml docuseal
version: '3.8'
services:
docuseal:
image: docuseal/docuseal:latest
ports:
- 3000:3000/tcp
volumes:
- /data
deploy:
restart_policy:
condition: any
Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a
persistent volume claim, and ports are exposed via a LoadBalancer service.
docuseal-data-0.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: docuseal-data-0
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
docuseal-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: docuseal
labels:
app: docuseal
spec:
replicas: 1
selector:
matchLabels:
app: docuseal
template:
metadata:
labels:
app: docuseal
spec:
containers:
- name: docuseal
image: docuseal/docuseal:latest
ports:
- containerPort: 3000
protocol: TCP
volumeMounts:
- name: docuseal-data-0
mountPath: /data
volumes:
- name: docuseal-data-0
persistentVolumeClaim:
claimName: docuseal-data-0
docuseal-service.yaml
apiVersion: v1
kind: Service
metadata:
name: docuseal
spec:
type: LoadBalancer
selector:
app: docuseal
ports:
- name: 3000-tcp
port: 3000
targetPort: 3000
protocol: TCP
Save this file as ~/.config/containers/systemd/docuseal.container
[Unit]
Description=DocuSeal
[Container]
Image=docuseal/docuseal:latest
ContainerName=docuseal
PublishPort=3000:3000/tcp
Volume=/data
[Service]
Restart=always
[Install]
WantedBy=default.targetThen reload systemd and start the service:
systemctl --user daemon-reload
systemctl --user start docusealFor a system-wide service, use /etc/containers/systemd/ and drop --user.
For more installation options, see the Documentation in our GitHub repo
<a href="https://www.docuseal.com">
<img alt="DocuSeal" src="https://www.docuseal.com/logo.png" width="80" />
<br>
</a>
DocuSeal
<a href="https://www.docuseal.com">
<img alt="DocuSeal" src="https://www.docuseal.com/logo.png" width="80" />
<br>
</a>
DocuSealOpen source document filling and signing
<img alt="Docker releases" src="https://img.shields.io/docker/v/docuseal/docuseal"><img src="https://img.shields.io/discord/1125112641170448454?logo=discord"/><img src="https://img.shields.io/twitter/follow/docusealco?style=social" alt="Follow @docusealco" />
DocuSeal is an open source platform that provides secure and efficient digital document signing and processing. Create PDF forms to have them filled and signed online on any device with an easy-to-use, mobile-optimized web tool.
✨ Live Demo | ☁️ Try in Cloud
Features
- PDF form fields builder (WYSIWYG)
- 12 field types available (Signature, Date, File, Checkbox etc.)
- Multiple submitters per document
- Automated emails via SMTP
- Files storage on disk or AWS S3, Google Storage, Azure Cloud
- Automatic PDF eSignature
- PDF signature verification
- Users management
- Mobile-optimized
- 7 UI languages with signing available in 14 languages
- API and Webhooks for integrations
- Easy to deploy in minutes
Pro Features
- Company logo and white-label
- User roles
- Automated reminders
- Invitation and identify verification via SMS
- Conditional fields and formulas
- Bulk send with CSV, XLSX spreadsheet import
- SSO / SAML
- Template creation with HTML API (Guide)
- Template creation with PDF or DOCX and field tags API (Guide)
- Embedded signing form (React, Vue, Angular or JavaScript)
- Embedded document form builder (React, Vue, Angular or JavaScript)
- Learn more
Deploy
|Heroku|Railway| |:--:|:---:| |
| 
|
|DigitalOcean|Render|
| 
| 
Docker
docker run --name docuseal -p 3000:3000 -v.:/data docuseal/docusealBy default DocuSeal docker container uses an SQLite database to store data and configurations. Alternatively, it is possible use PostgreSQL or MySQL databases by specifying the
DATABASE_URL env variable.Docker Compose
Download docker-compose.yml into your private server:curl https://raw.githubusercontent.com/docusealco/docuseal/master/docker-compose.yml > docker-compose.ymlRun the app under a custom domain over https using docker compose (make sure your DNS points to the server to automatically issue ssl certs with Caddy):
sudo HOST=your-domain-name.com docker compose upFor Businesses
Integrate seamless document signing into your web or mobile apps with DocuSeal
At DocuSeal we have expertise and technologies to make documents creation, filling, signing and processing seamlessly integrated with your product. We specialize in working with various industries, including Banking, Healthcare, Transport, Real Estate, eCommerce, KYC, CRM, and other software products that require bulk document signing. By leveraging DocuSeal, we can assist in reducing the overall cost of developing and processing electronic documents while ensuring security and compliance with local electronic document laws.Book a Meeting
License
Distributed under the AGPLv3 License. See LICENSE for more information. Unless otherwise noted, all files © 2023-2026 DocuSeal LLC.Tools
Serve DocuSeal 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 docuseal.example.com to http://docuseal:3000
Add this to your Caddyfile
docuseal.example.com {
reverse_proxy http://docuseal:3000
}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 docuseal - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:3000 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :3000 - Stop the other service, or pick a different host port. In
3000:3000only 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:3000. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, docuseal can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 3000
Image won't pull
Test the pull directly on the host: docker pull docuseal/docuseal: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 loginto 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 docuseal --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within docuseal's repo
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates