names provided by the --host-names flag do not resolve in a hyperkit vm
Open
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Without a datakit database the flag --host-names doesn't seem to resolve to any IP address in a LinuxKit/HyperKit vm.
This was tested by changing the linuxkit run hyperkit command to include --host-names some.host when launching vpnkit.
Contributor guide
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 by reproducing the issue with linuxkit run hyperkit and vpnkit using --host-names some.host, both with and without a datakit database. Trace how the --host-names value is handled in the LinuxKit/HyperKit setup and identify why it does not resolve to an IP address. Done means the supplied host name resolves in a HyperKit VM without a datakit database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100