Community Roadmap — What features do you want?

[amayer1983]

Docksentry Community Roadmap

Docksentry v1.8.0 is out with Discord and Webhook support! Now we want to hear from you.

What's your most wanted feature?

Here are some ideas we're considering — comment with a 👍 on your favorites or suggest something new:

Notification Channels

• Full Discord bot with slash commands (interactive like Telegram)
• Slack integration
• Email notifications
• Ntfy / Pushover native support

Update Management

• Scheduled maintenance windows (only update between 2-5 AM)
• Notification filters (only critical updates, severity levels)
• Container grouping / tags
• Dry-run mode (show what would update without doing it)
• Update approval workflow (require confirmation from multiple users)

Monitoring & Visibility

• REST API for external automation
• Prometheus metrics endpoint
• Container resource usage in /status
• Update changelog / release notes in notifications

Deployment

• Kubernetes support
• Unraid template

Note: ARM64 (Raspberry Pi) is already supported! Our Docker images are built for both linux/amd64 and linux/arm64.

How to vote

React with 👍 on items you want, or comment with your own ideas!

Every suggestion helps shape the future of Docksentry.

[jayjay3108]

Add topic id support for telegram bot

Useful when you use a groups with topics enabled, otherwise all messages will be sent in the general topic

Ideally to add the topic id in the web interface

[amayer1983]

@jayjay3108 Done! 🎉

Telegram Topic ID support is now available in v1.11.0.

How to use

Set the TELEGRAM_TOPIC_ID environment variable:

environment:
  - TELEGRAM_TOPIC_ID=12345

Or configure it in the Web UI under Settings → Telegram Topic ID.

All messages will be sent to the specified topic/thread. Leave empty to use the default (General) topic.

Thanks for the suggestion!

[amayer1983]

@jayjay3108 did you have the chance to test it?

[NotRetarded]

Digging the app for the little time that I have had it running vs Watchtower, WhatsUpDocker and Dockhand container monitoring that I've used.

I'm a big Discord user for getting alerts on my systems and containers that I run. Don't know if this is possible on your end, or the user end, but can you create a Discord bot that is something like BotFather on Telegram to communicate with DockSentry?

I'd also like to see Telegram as an Option versus as a requirement. Yes, I know that kinda defeats the point of what DockSentry can do, but it still serves a function as a container update notification tool or container auto-update. I really have no other use for Telegram other than running this app.

[amayer1983]

@hypnosis4u2nv Half of your suggestion is shipped in v1.12.0 (just released):

I'd also like to see Telegram as an Option versus as a requirement.

Done. BOT_TOKEN and CHAT_ID are now optional. You can run Docksentry fully headless with just the Web UI, just Discord, just a generic webhook, or any combination. At least one of them must be configured (validated at startup), but Telegram is no longer special.

To go headless, drop BOT_TOKEN/CHAT_ID from your environment and keep WEB_UI=true and/or your Discord webhook.

The two Telegram-only commands that didn't have a Web UI equivalent before — /cleanup and /selfupdate — are now buttons on the Settings page, so the Web UI is feature-complete for headless operation.

---

The other half:

can you create a Discord bot that is something like BotFather on Telegram to communicate with DockSentry?

That's a much bigger piece of work — interactive Discord requires implementing a slash-command bot (Discord HTTP interactions or gateway connection, command registration, button-component dispatch, …). It's a fair request but I want to wait and see how many users actually want full Discord interactivity vs. "Web UI is enough now that Telegram isn't required". Leaving it open as a v2.0 candidate.

Mind giving v1.12.0 a try in headless mode and letting me know how it feels compared to your previous setup?

[NotRetarded]

Thanks for considering my suggestions and implementing one of them. I'll test and report back once I've had time to put the fix you implemented for the API Timeout error through its paces. But the /cleanup is a welcome addition to the webui since I was using it via Telegram to cleanup the images.

Hopefully I won't have to open up another "bug" report lol. Maybe the development activity on this application will garner more attention and interest, so that you can start working on a version 2.0 candidate that integrates a Discord bot. You have more of a handle on the complexity to achieve it, and it appears to be an involved process so I can see why continued interest would be the motivation to delve into bringing it.

In the meantime, I'll explore possible alternate options like sending messages from Discord to the Telegram bot with an application like Activepieces or similar.

[NotRetarded]

@amayer1983 Just ran headless mode and everything appears to be running fine. Discord is getting notifications and the Webui is working as expected.

Switched back to running Telegram so I can test some more.

[NotRetarded]

@amayer1983

Regarding headless mode - can a schulde be setup to run cleanup or/and is that automatic after 24h?

[amayer1983]

You mean that a clean is done every 24 hours? Or only cleanup 24 hours old stuff?

[amayer1983]

@hypnosis4u2nv

Thanks for testing.

V2 will come after roughly 500 Stars 😄

[NotRetarded]

You mean that a clean is done every 24 hours? Or only cleanup 24 hours old stuff?

Under the Cleanup button on the settings page:

Cleanup removes unused Docker images older than 24h. Self-Update pulls the latest Docksentry image and recreates this container

So my question is whether this is done by default without user input or when the cleanup button is pressed?

The reason is that Self-Update works by default whenever the cron schedule is run. It also has its only Auto Self Update setting.

Which leads to my followup question: Can we attached a similar auto button, or even a schedule to run the Cleanup automatically without any user input?

[amayer1983]

@hypnosis4u2nv good question — and good idea on top.

The clarification first

So my question is whether this is done by default without user input or when the cleanup button is pressed?

Until v1.12.0, only when the button was pressed. The "older than 24h" part is the age filter (docker image prune --filter until=24h), not a schedule — it just makes sure that brand-new pulls or rollback candidates don't get deleted accidentally. Nothing automatic was happening.

The wording on the Settings page was misleading, that's on me. I've reworded it in v1.12.1 so it's explicit:

Image Cleanup — manual trigger only. Removes unused Docker images that are at least 24h old (the age filter prevents accidentally deleting images you just pulled). Enable Auto cleanup above to run this automatically after every successful auto-update.

And the feature you suggested — done

Can we attached a similar auto button, or even a schedule to run the Cleanup automatically without any user input?

Yes — shipped in v1.12.1:

• New AUTO_CLEANUP=true env var (default false)
• Or toggle "🧹 Auto cleanup" on the Settings page

When enabled, cleanup runs after every successful auto-update, not on a separate schedule. Reasoning: if no auto-update succeeded, there's nothing new to prune anyway, and running prune on every cron tick would just be noise. The 24h age filter still protects rollback candidates.

To enable:

docker pull amayer1983/docksentry:latest
docker compose up -d

Then either set AUTO_CLEANUP=true in your environment, or flip the toggle in the Web UI (persists across restarts).

V2 will come after roughly 500 Stars 😄

Still standing 😄 — and your testing/feedback is genuinely a big part of why v1 keeps getting better. Thanks.