Skip to content
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.

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

fix container for ipv6 #106

Merged
merged 1 commit into from
Oct 24, 2024
Merged

Conversation

sepauli
Copy link
Contributor

@sepauli sepauli commented Jun 18, 2024

Description

the tink-stack pod crashes on an ipv6 only cluster because the container can not handle IPv6 addresses

:~# kubectl logs -n tink-system tink-stack-6bbc556dd-znd6j
Defaulted container "tink-stack" out of: tink-stack, dhcp-relay
++ awk '/nameserver/ {print $2}' /etc/resolv.conf
+ POD_NAMESERVER=fd05:0000:0000::a
+ envsubst '$POD_NAMESERVER'
+ exec nginx -g 'daemon off;'
2024/06/03 16:23:37 [emerg] 3210953#3210953: invalid port in resolver "fd05:0000:0000::a" in /etc/nginx/nginx.conf:13
nginx: [emerg] invalid port in resolver "fd05:0000:0000::a" in /etc/nginx/nginx.conf:13

Why is this needed

We use an IPv6 only RKE2 Cluster and we need to start this container correctly.

Fixes: #99

How Has This Been Tested?

I tested the fix in our RKE2 IPv6 only cluster and it works. But i don't have an IPv4 environment for testing

@jacobweinstock jacobweinstock added the ready-to-merge Mergify: Ready for Merging label Oct 24, 2024
@mergify mergify bot merged commit 1a26103 into tinkerbell:main Oct 24, 2024
5 checks passed
@sepauli sepauli deleted the fix-nginx-container branch October 26, 2024 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Mergify: Ready for Merging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tink-stack nginx can't handle IPv6 adresses
2 participants