![Donetick]()
Donetick
Container
Chore and task tracker for households, with natural-language scheduling, assignee rotation, subtasks, points and rewards, labels, NFC tags and a calendar feed. Source: https://github.com/donetick/donetick
Image details
Source details
Configuration
TypeContainerlinuxdonetick/donetick:latest2021:2021/tcp/donetick-data/configDT_SQLITE_PATH=/donetick-data/donetick.dbDT_SERVER_PUBLIC_HOST=http://localhost:2021unless-stoppedTemplate by NotAFlightRisk
Report issueNotes
http://<your-host>:2021 and click Create one. Sign-ups stay open: everyone makes their own account, then asks to join your circle with the code under Settings --> Circle Settings, where you accept them. Once everyone's in, add DONETICK_DISABLE_SIGNUP=true to the container's environment. Crash reports and usage analytics stay off unless you tick them on the screen after signing up. Photo attachments and avatars need S3-compatible storage set up as their storage docs say, and uploads fail without it. The phone apps only connect over HTTPS with a real certificate, so they need a proxy in front. The SQLite database lives in the data volume, and the generated login secret and settings (selfhosted.yaml) in the config one. Docs: docs.donetick.comStandalone Install
Select an install method, to see config/commands for deploying Donetick
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- 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 Donetick, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see donetick/donetick for app-specific guidance.
Serve Donetick 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 donetick.example.com to http://donetick:2021
Add this to your Caddyfile
donetick.example.com {
reverse_proxy http://donetick:2021
}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 donetick - 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:2021 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :2021 - Stop the other service, or pick a different host port. In
2021:2021only 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:2021. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, donetick can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 2021
Image won't pull
Test the pull directly on the host: docker pull donetick/donetick: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, arm/v7, arm64/v8 - 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 donetick --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 on donetick/donetick
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Donetick 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 Donetick needs bundled into one download. This template pulls donetick/donetick:latest, which Docker fetches once (about 31 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. Donetick's comes from Docker Hub, published by donetick.
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 v0.1.82. 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, arm64/v8, 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 2021:2021 means it's reachable on port 2021 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
2021:2021
Volumes
A volume is where Donetick 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:
/donetick-dataas a volume Docker manages for you/configas 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. Donetick takes 2 of them, all with defaults you can leave alone or tweak:
DT_SQLITE_PATH, defaults to/donetick-data/donetick.db. Keeps the database in the data volume, so leave it as it is.DT_SERVER_PUBLIC_HOST, defaults tohttp://localhost:2021. Where you'll open it, like http://192.168.1.10:2021. The calendar feed link is built from this.
Restart policy
The restart policy here is unless-stopped, so Docker restarts Donetick 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 Donetick 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 donetick. That's what you'll spot in the containers list and use in commands like docker logs donetick.
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
Donetick 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 Donetick up. Add the template list to Portainer once, then deploying Donetick is a click rather than a wall of config.