#145: Include bind-utils or similar in base image
-------------------------------+---------------------
Reporter: jfindley | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future
Component: Docker Host Image | Resolution:
Keywords: |
-------------------------------+---------------------
Comment (by mmicene):
(mattdm ticket:145#comment:8) Unfortunately, bind-utils has a bunch
of
deps, including as currently packaged GeoIP and the GeoIP database.
I did a quick F23 compose today to check, we only add 4 packages for bind-
utils. GeoIP is already included in the latest tree. For this particular
add, I don't see a lot of bloat.
Having an alternative like busybox as a way to first try to satisfy a new
tool request would be interesting. Especially since there's a decent
reduction in overhead to test and no net add.
> (jlebon) How about glibc's getent?
(walters ticket:145#comment:8) Yes, I am curious what use case isn't
covered by
this.
I think `getent` is just unfamiliar to most folks to use and understand.
You *can* change the dns host being queried by changing /etc/hosts, but
how many folks know that?
Pointing to Google over having one of several common tools needs a pretty
strong argument. Especially if we can get busybox in to cover things as a
first resort, with the addition of the official packages as a fall back if
there are additional dependencies or unexpected behavior.
The problem would be adding the symlinks for busybox to an expected place
for users. There was some talk on IRC on how to do this, but it's just as
important to have `nslookup` in the path with a standard invocation if we
go the busybox route, or `busybox nslookup` is as much of a "RTFSE" issue
as explaining getent.
--
Ticket URL: <
https://fedorahosted.org/cloud/ticket/145#comment:13>
cloud <
https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System