Skip to content

fix: keep Tailscale runtime mount fresh - #19

Merged
alihussainiF1 merged 1 commit into
mainfrom
ali/fix-tailscale-runtime-mount
Aug 12, 2026
Merged

fix: keep Tailscale runtime mount fresh#19
alihussainiF1 merged 1 commit into
mainfrom
ali/fix-tailscale-runtime-mount

Conversation

@alihussainiF1

Copy link
Copy Markdown
Collaborator

What changed

Mount the Tailscale runtime directory in every Deploy Manager Compose configuration instead of bind-mounting only tailscaled.sock.

Why

When tailscaled restarts, it replaces the Unix socket inode. Long-running Deploy Manager containers kept the stale socket bind mount and all Tailscale SSH server checks and deployments failed until the containers were restarted. Mounting the containing directory lets the container resolve the replacement socket.

Validation

  • docker compose config --quiet
  • docker compose -f docker-compose.dev.yml config --quiet
  • deploy image Compose configuration validation
  • git diff --check
  • Recovered production runner verified with matching host and container socket inode and a successful AllEyes deployment

@alihussainiF1
alihussainiF1 marked this pull request as ready for review August 12, 2026 21:13
@alihussainiF1
alihussainiF1 merged commit 51fe08b into main Aug 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant