Alloy docker image using google DNS?

Grafana Alloy
1

I have been using the alloy docker image for a bit now. I started having an issue where I am running it on my local network, and instead of using our corporate DNS the image appears to be using google DNS instead? I did check and the container is linked to the default bridge network

I noticed in the alloy logs for on the container that I see things like:
dial tcp: lookup <Loki-host> on 8.8.8.8:53: no such host

I can run Alloy just fine on the host that is running docker.

And I checked the /etc/resolve.conf in the container and it looks right to me.

Any ideas what I might be missing?

2

By running on your local network do you mean bare metal installation?

Docker container is supposed to use host DNS resolution unless specified.

3

Yea, sorry. Imprecise language…
So I am running the docker image on a host. And in the alloy config it is using URLs to external resources that exist on my local network.
For some reason it appears to be doing DNS resolution differently in the docker image than the host it is running on; which I don’t understand…

I confess I believe this is a problem with my docker config, but I do not know what to look at

4
  1. What is your Docker command for running Alloy?
  2. Check /etc/resolv.conf in your Alloy container and see if it matches your host configuration.
5

Yep, I mentioned that in the OP. It is basically the same.

6

Try specifying DNS server (i believe it’s --dns when running Docker container) and see if that helps. I just tested our setup and I don’t see this issue.

What host OS are you running?

7

Yea, that did work.
The host is Ubuntu