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: DOCKER_HOST handling of unix sockets #1045

Conversation

serverwentdown
Copy link
Contributor

@serverwentdown serverwentdown commented Apr 9, 2022

In a580edb, GetHost() introduced code to handle the DfD use case. However, it also caused "unix:///" DOCKER_HOST values to be parsed incorrectly. This resulted in kubeconfigs containing "unix" as the hostname.

This patch ensures all "unix:///" DOCKER_HOST values are parsed as an empty host (and thus set as 0.0.0.0 in kubeconfig)

@serverwentdown serverwentdown changed the title fix: `DOCKER_HOST handling of unix sockets fix: DOCKER_HOST handling of unix sockets Apr 9, 2022
In a580edb, GetHost() introduced code
to handle the DfD use case. However, it also caused "unix:///" DOCKER_HOST
values to be parsed incorrectly. This resulted in kubeconfigs containing
"unix" as the hostname.

This patch ensures all "unix:///" DOCKER_HOST values are parsed as an
empty host (and thus set as 0.0.0.0 in kubeconfig)
@serverwentdown serverwentdown force-pushed the fix-docker-host-handling-on-unix-sockets branch from d915ae6 to 0c1c641 Compare April 9, 2022 15:02
@iwilltry42 iwilltry42 merged commit f644103 into k3d-io:main May 13, 2022
@iwilltry42
Copy link
Member

Thank you @serverwentdown ! 👍

@iwilltry42 iwilltry42 added this to the v5.5.0 milestone May 13, 2022
@iwilltry42 iwilltry42 added enhancement New feature or request docs Documentation labels May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants