Start containers only when needed #1358

New Issue

MrUnknownDE · 2026-04-05T19:10:48+02:00

MrUnknownDE commented

2026-04-05 19:10:48 +02:00

Originally created by @MyWay on 6/12/2025

Now that Newt has access to the Docker socket, would it make sense to explore support for starting and stopping containers dynamically based on usage patterns?

For example, some services are only needed sporadically and could be started when a request is received and stopped afterwards. This could help reduce resource usage for less frequently accessed containers.

Would this be within the scope of Pangolin? I know some solutions for caddy and other reverse proxies exist, but it may be cool to integrate it within pangolin ecosystem.

*Originally created by @MyWay on 6/12/2025* Now that Newt has access to the Docker socket, would it make sense to explore support for starting and stopping containers dynamically based on usage patterns? For example, some services are only needed sporadically and could be started when a request is received and stopped afterwards. This could help reduce resource usage for less frequently accessed containers. Would this be within the scope of Pangolin? I know some solutions for caddy and other reverse proxies exist, but it may be cool to integrate it within pangolin ecosystem.

MrUnknownDE closed this issue

2026-04-05 19:10:48 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1358