Score:0

DNS resolution for a docker container running on k8s-installed-host follows k8s dns resolution

in flag

I have k8s installed on a ubuntu20.04 with coredns as custom dns service.

enter image description here

Then i deployed an empty ubuntu docker container using

docker run -it --name test-ubuntu ubuntu:20.04 /bin/bash

Then for some reason, /etc/resolve.conf in the test-ubuntu container looks like enter image description here

which is clearly something only pods launched with k8s should have. My guess coredns is somehow affecting other docker containers too but i do not understand how this can happen.

Andrew Skorkin avatar
tr flag
Could you please add information about how you deployed k8s cluster, its version? Have you configured CoreDNS somehow?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.