Skip to content

Restore EC2 DNS after legacy VPN shutdown #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Merged
protostatis merged 1 commit into from
Jun 1, 2026
Merged

Restore EC2 DNS after legacy VPN shutdown #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,13 @@ jobs:
echo "Disabling legacy WireGuard before network operations."
sudo systemctl disable --now wg-quick@wg0 2>/dev/null || true

# wg-quick can leave the host pointed at VPN DNS after shutdown.
# Restore the EC2 VPC resolver so git fetch and docker pull can
# resolve github.com/ghcr.io before the deploy proceeds.
echo "Restoring EC2 DNS resolver."
sudo sh -c 'printf "nameserver 169.254.169.253\noptions timeout:2 attempts:3\n" > /etc/resolv.conf'
getent hosts github.com >/dev/null

# Pull latest code. Preserve any EC2-local edits so deployment can
# move to the release tag without discarding operational changes.
git fetch --tags origin
Expand Down
Loading