We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
While setting up Headscale, I noticed that the Headscale developers deliberately not use latest tag.
Since the config.yaml has specific settings related to the version, this leads to a not working docker container.
Their current recommendation for the container deployment is: v0.23.0-alpha5
They additionally changed: command: headscale serve to command: server and the volume mounts.
command: headscale serve
command: server
version: "3.9" services: headscale: container_name: headscale image: headscale/headscale:0.23.0-alpha5 restart: unless-stopped command: serve volumes: - ./config:/etc/headscale - /lib:/var/lib/headscale - /run:/var/run/headscale
The config.yaml should be pulled from the documentation with the correct tag.
The text was updated successfully, but these errors were encountered:
Have you been able to deploy it with traefik? I'm struggling
Sorry, something went wrong.
Yea, see this issue why latest does not work. juanfont/headscale#1810 AFAIK current stable is 22.3 but check the release page for the correct version to use https://github.com/juanfont/headscale/releases
No branches or pull requests
Hi,
While setting up Headscale, I noticed that the Headscale developers deliberately not use latest tag.
Since the config.yaml has specific settings related to the version, this leads to a not working docker container.
Their current recommendation for the container deployment is: v0.23.0-alpha5
They additionally changed:
command: headscale serve
tocommand: server
and the volume mounts.The config.yaml should be pulled from the documentation with the correct tag.
The text was updated successfully, but these errors were encountered: