Hi Ben, Ben Greear <[email protected]> writes:
>> Did you consider using a container (e.g. docker) for such a task ? Easy to >> set >> up and you'll have your feature not only for wget. IMO, that is much more >> flexible. (It was Giuseppe's idea during a private talk). > > Containers will not work for me. I need to scale to thousands of > instances on modest hardware. I'm certain the libcares and binding > approach will work because we do similar things with curl and other > programs already. how modest is this hardware? I tried to build a minimal Docker container for wget on top of Alpine: Dockerfile: FROM alpine RUN apk add --update wget WORKDIR /out ENTRYPOINT ["/usr/bin/wget"] and simply running (192.168.1.13 is an internal DNS server): docker run --dns=192.168.1.13 --rm -v $(pwd):/out:Z wget wdserver takes around 5M, plus the docker daemon. If this is not enough, you can even just run wget in a chroot, and provide a different /etc/resolv.conf. Cheers, Giuseppe
