Unable to build the container: Errors were encountered while processing: heimdal-kdc

[olivergondza]

I am building the container to give it a try. The ./kdc build fails for me with following:

...
Setting up krb5-config (2.3) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Setting up libfile-copy-recursive-perl (0.38-1) ...
Setting up tcpd (7.6.q-25) ...
Setting up update-inetd (4.43) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Setting up heimdal-clients (1.6~git20131207+dfsg-1ubuntu1.1) ...
update-alternatives: using /usr/bin/kftp to provide /usr/bin/ftp (ftp) in auto mode
update-alternatives: using /usr/bin/ktelnet to provide /usr/bin/telnet (telnet) in auto mode
update-alternatives: using /usr/bin/krsh to provide /usr/bin/rsh (rsh) in auto mode
update-alternatives: using /usr/bin/krcp to provide /usr/bin/rcp (rcp) in auto mode
update-alternatives: using /usr/bin/kpagsh to provide /usr/bin/pagsh (pagsh) in auto mode
Setting up openbsd-inetd (0.20091229-2ubuntu3) ...
invoke-rc.d: policy-rc.d denied execution of stop.
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for ureadahead (0.100.0-16) ...
Setting up heimdal-kdc (1.6~git20131207+dfsg-1ubuntu1.1) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
kstash: writing key to `/var/lib/heimdal-kdc/m-key'
kstash: writing master key file: No such file or directory
dpkg: error processing package heimdal-kdc (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
 heimdal-kdc
E: Sub-process /usr/bin/dpkg returned an error code (1)
The command '/bin/sh -c apt-get -y install heimdal-kdc' returned a non-zero code: 100

• Docker version 1.12.1, build 23cf638
• Commit 3c80d27

[seanf]

@olivergondza I had the same problem. I think the default generated kerberos config doesn't like Red Hat hostnames.

Try this:

KDC_CONFIG=samples/kdc.json ./kdc build

[seanf]

@olivergondza This also seems to work, and fits better with examples on the home page:

KDC_CLIENT=hostname KDC_DOMAIN_NAME=example.com ./kdc build

You may also want to remove --no-cache from docker build in the kdc script, as a temporary measure, to save your sanity while tweaking these settings.