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

Docker Hub: No tag 'headscale:latest' anymore #659

New Issue
Closed
opened 2025-12-29 02:21:42 +01:00 by adam · 9 comments
adam commented 2025-12-29 02:21:42 +01:00
Owner
Copy Link

Originally created by @x86dev on GitHub (Mar 3, 2024).

When pulling Headscale via Docker Hub (https://hub.docker.com/r/headscale/headscale), i.e. via docker pull headscale/headscale, it errors out with "manifest for headscale/headscale:latest not found: manifest unknown: manifest unknown".

Only pulling "headscale/headscale:unstable" works. IIRC there was a "headscale/headscale:latest" tag before -- any reason why this vanished?

Originally created by @x86dev on GitHub (Mar 3, 2024). When pulling Headscale via Docker Hub (https://hub.docker.com/r/headscale/headscale), i.e. via `docker pull headscale/headscale`, it errors out with "manifest for headscale/headscale:latest not found: manifest unknown: manifest unknown". Only pulling "headscale/headscale:unstable" works. IIRC there was a "headscale/headscale:latest" tag before -- any reason why this vanished?
adam added the stalebug labels 2025-12-29 02:21:42 +01:00
adam closed this issue 2025-12-29 02:21:42 +01:00
adam commented 2025-12-29 02:21:43 +01:00
Author
Owner
Copy Link

@ohdearaugustin commented on GitHub (Mar 3, 2024):

We dropped the latest tag for now, please use tagged releases.

This has two reasons:

  1. using the latest tag is bad practice
  2. We changed the pipeline to release the docker images and accidentally tagged a pre-release with the latest tag. Therefore we manually had to remove the tag.

Announcements on Discord:

Sorry, this message is a bit late, but we want to warn people that by accident, the alpha release got pushed to the latest tag which can cause problems.

We recommend you always tag a specific version to ensure you are in control of your own deployments, for ours and other containers.

As for the change, the alpha container changed the entrypoint so in the general case it should crash loop and not run the new version.

We are working on correcting the tags.

The docker tags issue we had with the previous issue should now be resolved, as part of this, we have chosen to untag latest for the time being, and we expect it to be reinstated when there is a new stable release, but we strongly recommend people to use version specific tags.
@ohdearaugustin commented on GitHub (Mar 3, 2024): We dropped the latest tag for now, please use tagged releases. This has two reasons: 1. using the latest tag is bad practice 2. We changed the pipeline to release the docker images and accidentally tagged a pre-release with the latest tag. Therefore we manually had to remove the tag. Announcements on Discord: ``` Sorry, this message is a bit late, but we want to warn people that by accident, the alpha release got pushed to the latest tag which can cause problems. We recommend you always tag a specific version to ensure you are in control of your own deployments, for ours and other containers. As for the change, the alpha container changed the entrypoint so in the general case it should crash loop and not run the new version. We are working on correcting the tags. ``` ``` The docker tags issue we had with the previous issue should now be resolved, as part of this, we have chosen to untag latest for the time being, and we expect it to be reinstated when there is a new stable release, but we strongly recommend people to use version specific tags. ```
adam commented 2025-12-29 02:21:43 +01:00
Author
Owner
Copy Link

@x86dev commented on GitHub (Mar 4, 2024):

Ok, thanks for clarifying this!

@x86dev commented on GitHub (Mar 4, 2024): Ok, thanks for clarifying this!
adam commented 2025-12-29 02:21:43 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Mar 5, 2024):

but with that autoupdates with watchtower are not possible anymore

@celevra commented on GitHub (Mar 5, 2024): but with that autoupdates with watchtower are not possible anymore
adam commented 2025-12-29 02:21:43 +01:00
Author
Owner
Copy Link

@x86dev commented on GitHub (Mar 5, 2024):

True, ran into that as well.

@x86dev commented on GitHub (Mar 5, 2024): True, ran into that as well.
adam commented 2025-12-29 02:21:44 +01:00
Author
Owner
Copy Link

@ohdearaugustin commented on GitHub (Mar 5, 2024):

Please read the second part, they will be reestablished with the new stable release. Therefore I don't see a problem.

@ohdearaugustin commented on GitHub (Mar 5, 2024): Please read the second part, they will be reestablished with the new stable release. Therefore I don't see a problem.
adam commented 2025-12-29 02:21:44 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 7, 2024):

Which version is the latest now?

@ghost commented on GitHub (Mar 7, 2024): Which version is the latest now?
adam commented 2025-12-29 02:21:44 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Mar 7, 2024):

0.22.3 is the latest stable version.

@kradalby commented on GitHub (Mar 7, 2024): 0.22.3 is the latest stable version.
adam commented 2025-12-29 02:21:44 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 6, 2024):

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

@github-actions[bot] commented on GitHub (Jun 6, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:21:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 13, 2024):

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

@github-actions[bot] commented on GitHub (Jun 13, 2024): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 bug stale
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#659
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?