Tailscale container hook fails on images without apt/apk/pacman
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 253
- Forks
- 106
- Avg merge
- 6d 22h
- Merged PRs (30d)
- 12
Description
share/docker/tailscale_container_hook only detects apt-get, apk, and pacman. Anything else fails with ERROR: Detection from Package Manager failed! and the container starts without Tailscale.
Example with searxng/searxng (Void Linux base, no xbps in runtime image):
docker run --rm --entrypoint sh searxng/searxng:latest -c '
wget -qO /tmp/hook https://raw.githubusercontent.com/unraid/webgui/master/share/docker/tailscale_container_hook
ORG_ENTRYPOINT=/bin/true ORG_CMD= ORG_POSTARGS= sh /tmp/hook
'
Detecting Package Manager...
ERROR: Detection from Package Manager failed!
ERROR: Unraid Docker Hook script throw an error!
Starting container without Tailscale!
I'll open a PR adding xbps-install detection plus a static-binary fallback (static jq + the existing static Tailscale tarball) for images with no supported package manager. The Tailscale tarball already works inside searxng/searxng - verified tailscaled boots and reaches the control plane - so the only missing piece is jq, which also ships as a static binary.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with share/docker/tailscale_container_hook and reproduce the failure using the searxng/searxng command in the issue. Trace package-manager detection and the existing static Tailscale tarball path, then verify the hook handles an image without apt-get, apk, or pacman and that tailscaled reaches the control plane.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100