Upgrade path from Binary to .deb / .rpm #474

Closed
opened 2025-12-29 01:30:01 +01:00 by adam · 6 comments
Owner

Originally created by @Porco-Rosso on GitHub (Apr 14, 2023).

The installation docs do not reflect the current .deb and .rpm releases, as they mention direct go binaries instead.

  1. How does one install headscale using the new release format?
  2. How does one upgrade from the previous method to the new one, given the manual SystemD install process?

This is both a matter of documentation and upgrade functionality. I assume eventually headscale will be released on default package mangers, at which point the process should be simplified.

Originally created by @Porco-Rosso on GitHub (Apr 14, 2023). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the issue in this language. --> <!-- If you have a question, please consider using our Discord for asking questions --> The installation docs do not reflect the current .deb and .rpm releases, as they mention direct go binaries instead. 1. How does one install headscale using the new release format? 2. How does one upgrade from the previous method to the new one, given the manual SystemD install process? This is both a matter of documentation and upgrade functionality. I assume eventually headscale will be released on default package mangers, at which point the process should be simplified.
adam added the stalebug labels 2025-12-29 01:30:01 +01:00
adam closed this issue 2025-12-29 01:30:01 +01:00
Author
Owner

@kradalby commented on GitHub (Apr 19, 2023):

Hi, I will work on documentation on how to install it on various platforms today; but in the mean time:

  1. Download the file that is associated with your linux distribution; .deb for Debian/Ubuntu and .rpm for Fedora/Alma/CentOS and use the platform specific installation instructions to install them.
  2. The ideal would be to remove everything from before, except for the config.yaml, and use the method above.

We do not aspire to add it to the package managers, and we will most likely just release it via Github as now.

@kradalby commented on GitHub (Apr 19, 2023): Hi, I will work on documentation on how to install it on various platforms today; but in the mean time: 1. Download the file that is associated with your linux distribution; .deb for Debian/Ubuntu and .rpm for Fedora/Alma/CentOS and use the platform specific installation instructions to install them. 2. The ideal would be to remove everything from before, except for the config.yaml, and use the method above. We do not aspire to add it to the package managers, and we will most likely just release it via Github as now.
Author
Owner

@Porco-Rosso commented on GitHub (Apr 20, 2023):

I see the new documentation is up, so I will close this.

This was a roadbump for my transition, but all is good now.
https://github.com/juanfont/headscale/issues/1342#issuecomment-1516779155

@Porco-Rosso commented on GitHub (Apr 20, 2023): I see the new documentation is up, so I will close this. This was a roadbump for my transition, but all is good now. https://github.com/juanfont/headscale/issues/1342#issuecomment-1516779155
Author
Owner

@Porco-Rosso commented on GitHub (Apr 20, 2023):

As I mentioned on the other thread still having problems with permissions, /var/run/headscale/ in particular

@Porco-Rosso commented on GitHub (Apr 20, 2023): As I mentioned on the other thread still having problems with permissions, `/var/run/headscale/` in particular
Author
Owner

@loprima-l commented on GitHub (Apr 28, 2023):

Please make sure to run this with user being the user that launches Headscale :
sudo chown user /var/run/headscale

@loprima-l commented on GitHub (Apr 28, 2023): Please make sure to run this with user being the user that launches Headscale : `sudo chown user /var/run/headscale`
Author
Owner

@github-actions[bot] commented on GitHub (Oct 26, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Oct 26, 2023): This issue is stale because it has been open for 180 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 9, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Nov 9, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#474