starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Ability to reload headscale in docker container #531

New Issue
Closed
opened 2025-12-29 02:19:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:19:35 +01:00
Owner
Copy Link

Originally created by @winterheart on GitHub (Jul 10, 2023).

Why

Currently headscale supports reloading config on kill -HUP signal which has no downtime, but headscale in docker do not have kill or equivalent command. I forced to restart whole container to apply changes which may result unavailability of service.

Description

It would be great if headscale will watch config.yaml and acl.yaml files for changes and gracefully reloads them on changes. Less elegant but more straightforward approach would be adding kill command into docker image, so admin can call docker exec kill -HUP ... to reload config inside container.

Originally created by @winterheart on GitHub (Jul 10, 2023). <!-- We typically have a clear roadmap for what we want to improve and reserve the right to close feature requests that does not fit in the roadmap, or fit with the scope of the project, or we actually want to implement ourselves. Headscale is a multinational community across the globe. Our language is English. All bug reports needs to be in English. --> ## Why Currently headscale supports reloading config on `kill -HUP` signal which has no downtime, but headscale in docker do not have `kill` or equivalent command. I forced to restart whole container to apply changes which may result unavailability of service. <!-- Include the reason, why you would need the feature. E.g. what problem does it solve? Or which workflow is currently frustrating and will be improved by this? --> ## Description It would be great if headscale will watch config.yaml and acl.yaml files for changes and gracefully reloads them on changes. Less elegant but more straightforward approach would be adding `kill` command into docker image, so admin can call `docker exec kill -HUP ...` to reload config inside container. <!-- A clear and precise description of what new or changed feature you want. -->
adam added the enhancement label 2025-12-29 02:19:35 +01:00
adam closed this issue 2025-12-29 02:19:35 +01:00
adam commented 2025-12-29 02:19:36 +01:00
Author
Owner
Copy Link

@winterheart commented on GitHub (Jul 10, 2023):

Ok, after quick digging, I found that I can actually docker kill --signal HUP headscale which forces to reload config, but still, it would be great if headscale will automatically reloads configs on changes.

@winterheart commented on GitHub (Jul 10, 2023): Ok, after quick digging, I found that I can actually `docker kill --signal HUP headscale` which forces to reload config, but still, it would be great if headscale will automatically reloads configs on changes.
adam commented 2025-12-29 02:19:36 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Aug 11, 2023):

Dupe https://github.com/juanfont/headscale/issues/173

@juanfont commented on GitHub (Aug 11, 2023): Dupe https://github.com/juanfont/headscale/issues/173
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#531
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?