@@ -4,10 +4,13 @@ It's a [dnsmasq][dnsmasq] Docker image. It is only 6 MB in size. It is just an `
...
@@ -4,10 +4,13 @@ It's a [dnsmasq][dnsmasq] Docker image. It is only 6 MB in size. It is just an `
## Usage
## Usage
Use a tag other than `latest` if you are using this image in a production setting. There is at tag for dnsmasq 2.71 (`andyshinn/dnsmasq:2.72`) which is the latest on Alpine Linux 3.2. I will release an updated tag (`andyshinn/dnsmasq:2.75`) when Alpine Linux 3.3 has a stable release.
It is usually a good idea to use a tag other than `latest` if you are using this image in a production setting. There are currently two tags to choose from:
[dnsmasq][dnsmasq] requires `NET_ADMIN` capabilities to run correctly. Start it with something like `docker run -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN andyshinn/dnsmasq`.
*`andyshinn/dnsmasq:2.72`: dnsmasq 2.71 based on Alpine 3.2
*`andyshinn/dnsmasq:2.75`: dnsmasq 2.75 based on Alpine 3.3
The configuration is all handled on the command line (no wrapper scripts here). The `ENTRYPOINT` is `dnsmasq -k` to keep it running in the foreground. If you wanted to send requests for an internal domain (such as Consul) you can forward the requests upstream using something like `docker run -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN andyshinn/dnsmasq -S /consul/10.17.0.2`. This will send a request for `redis.service.consul` to `10.17.0.2`
[dnsmasq][dnsmasq] requires `NET_ADMIN` capabilities to run correctly. Start it with something like `docker run -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN andyshinn/dnsmasq:2.75`.
The configuration is all handled on the command line (no wrapper scripts here). The `ENTRYPOINT` is `dnsmasq -k` to keep it running in the foreground. If you wanted to send requests for an internal domain (such as Consul) you can forward the requests upstream using something like `docker run -p 53:53/tcp -p 53:53/udp --cap-add=NET_ADMIN andyshinn/dnsmasq:2.75 -S /consul/10.17.0.2`. This will send a request for `redis.service.consul` to `10.17.0.2`
