[16.04] debconf: delaying package configuration, since apt-utils is not installed #319
Comments
hyperknot
changed the title
hyperknot
changed the title
|
Upstream problem; I can confirm this with clean image |
|
Did you find any solutions for this? @hyperknot @FranklinYu |
|
yes, I'm installing it myself On Thursday, 8 September 2016, aa notifications@github.com wrote:
|
|
@aa21 I did not. The Debian-Docker guys thought this is an issue of APT incorrectly requiring the (unnecessary) package, and refused to fix it, since this is just a warning not able to stop you from anything. I guess they are too busy for it. Good to hear that @hyperknot is trying to fix it. I am looking forward to his solution/workaround. |
|
My solution is just to put a line in the docker file and it fixes the problem. |
|
Thanks @hyperknot and @FranklinYu. |
|
It did not worked for me =/ |
|
it's the only red command I now get when setting up my jekyll x86 base image... |
didn't work for me too. |
|
It is a harmless 1 line warning message. The command does get installed, and following apt-get commands do not show any error / warning messages. |
|
I started making an updated fork of this project, containing Ubuntu 16.04 fixes, including this one. Have a look here: |
When I install apt-utils before the rest of apt packages, I only get Apparently this is also a harmless warning that can be avoided by setting If anyone is wondering what the best-practice way to set this variable is, this is the best info I could find moby/moby#4032 (comment) . The key takeaway there is make sure you don't use I wonder though, what if you're installing a package that does depend on interactive configuration? Does apt-get just fail, or will it just silently leave the package unconfigured? |
|
I don't think apt-get allows packages which only work in interactive mode. So all packages must work in noninteractive mode. What I do is I set in the beginning of the Docker file At the very end. This way both interactive and non-interactive modes get set. |
|
@hyperknot Why two |
|
They are totally different. ENV is persistent in the image. It'd still need two cases here. |
|
But why do you need to persist it (which overrides the default)? The default frontend works for me. In addition, |
|
The default gives a warning about falling back to teletype. So setting it
to teletype fixes that.
…On 2017. Jan 16., Mon at 4:53, Franklin Yu ***@***.***> wrote:
But why do you need to persist it (which overrides the default)? The
default frontend works for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#319 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAeKj72VDDMFMxk_L-p1n6yhkOkNfgnIks5rSum3gaJpZM4JMfSU>
.
|
|
Yes, I just confirmed that. I thought the default only gives warning when installing packages in Dockerfile. I missed that because the warning was not highlighted as red (of course), and that doesn't happen on normal Ubuntu. However, |
|
I noticed that as well. But Teletype is the one it is falling back
automatically also "Falling back to Teletype", so I believe it's a
reasonable choice.
…On 16 January 2017 at 21:04, Franklin Yu ***@***.***> wrote:
Yes, I just confirmed that. I thought the default only gives warning when
installing packages in Dockerfile. I missed that because the warning was
not highlighted as red (of course), and that doesn't happen on normal
Ubuntu. However, teletype is not a known value for DEBIAN_FRONTEND
according to documentation online
<https://www.debian.org/releases/jessie/amd64/ch05s03.html.en#installer-args>
(??), while the newt mentioned as default in documentation still produces
the warning for me (???).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#319 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAeKj93TyLDBEMQsBsUJVRci1sFuTsicks5rS81fgaJpZM4JMfSU>
.
|
|
Being that this is an upstream issue, I am closing this issue. It looks like there is a viable workaround and this issue will remain for posterity. |
|
FWIW But I am still getting the warnings about apt-utils. |
|
@aairey Did you try adding this to your Dockerfile?
|
|
@aairey We discussed about why we need |
|
@Theaxiom this just installs @FranklinYu it works for me just using |
|
@aairey Unfortunately, I think that is indeed the only way to make the error message go away. From what I understand it is a no-op. |
|
@danielxfr how about: FROM ...
ARG DEBIAN_FRONTEND=noninteractive
RUN \
apt-get update -y && \
apt-get install -y apt-utils 2>&1 | grep -v "debconf: delaying package configuration, since apt-utils is not installed" && \
apt-get install -y --no-install-recommends package1,package2,... |
|
I will reopen this issue until we come to a conclusion. |
|
Building off of #319 (comment) from @sebthom; if you use bash, you can keep STDERR text separate from STDOUT and apply the grep pattern only in the STDERR text: |
`debconf: delaying package configuration, since apt-utils is not installed` error is appearing in pipeline runs, and possibly causing failures on DEV e2e runs. Seems to be an [underlying issue in ubuntu image](phusion/baseimage-docker#319)
Fixed problem with help these resources: https://stackoverflow.com/questions/51023312/docker-having-issues-installing-apt-utils phusion/baseimage-docker#319
|
This is also an issue exists on Ubuntu's 18.04 image |
|
I too have this apt-utils problem and it's really bringing the grade of development down, it says unable to.further configure after this. |
|
Having also the apt-utils issue and when I want to install gcc of a specific version it also does not export it in the PATH correctly... after adding the install line of apt-utils it at least added the gcc files into the bin directory. RUN \
set -eux \
&& apt-get -y update \
&& apt-get install -y apt-utils \
&& apt-get -y install --no-install-recommends --no-install-suggests --fix-missing bash-static \
&& apt-get -y install gcc-4.8 \
&& apt-get -y install make \
&& cp /bin/bash-static /shthen I get the following errors on make gcc and so on: After some googling I found this here added the dialog apt-utils line but the error still persists not sure if both problems are related. Anyone else having the same behaviour on ubuntu:18.04 image? RUN \
set -eux \
&& apt-get -y update \
&& apt-get install -y dialog apt-utils \
&& apt-get -y install --no-install-recommends --no-install-suggests --fix-missing bash-static \
&& apt-get -y install gcc-4.8 \
&& apt-get -y install make \
&& cp /bin/bash-static /sh |
|
Update: just adding seems to do the trick for the ubuntu image. gcc is still not found in the path but that I can fix by hand. ENV DEBIAN_FRONTEND="noninteractive"
RUN ln -s /usr/bin/gcc-4.8 /usr/bin/gcc |
|
The behavior is controlled by the configuration setting: The default setting is configured via "/etc/apt/apt.conf.d/70debconf": To disable the setting permanently: RUN set -x \
&& sed -Ei 's|^(DPkg::Pre-Install-Pkgs .*)|#\1|g' /etc/apt/apt.conf.d/70debconf \
&& apt-get update \
&& apt-get upgrade -yTo disable the setting temporarily: RUN set -x \
&& mv /etc/apt/apt.conf.d/70debconf . \
&& apt-get update \
&& apt-get install -y apt-utils \
&& mv 70debconf /etc/apt/apt.conf.d \
&& apt-get upgrade -yShow less debconf warnings: Here is an example Docker file including all methods mentioned above, pick the one that fits your use case. ARG IMAGE="ubuntu:16.04"
FROM ${IMAGE}
ARG DEBIAN_FRONTEND="noninteractive"
ARG DEBCONF_NOWARNINGS="yes"
ARG DEBCONF_TERSE="yes"
ARG APT="apt-get -qq -y"
ARG LANG="C.UTF-8"
# Configure APT
RUN set -x \
&& echo "debconf debconf/frontend select ${DEBIAN_FRONTEND}" | debconf-set-selections \
&& echo 'APT::Install-Recommends "false";' | tee /etc/apt/apt.conf.d/99install-recommends \
&& echo 'APT::Get::Assume-Yes "true";' | tee /etc/apt/apt.conf.d/99assume-yes \
&& sed -Ei 's|^(DPkg::Pre-Install-Pkgs .*)|#\1|g' /etc/apt/apt.conf.d/70debconf \
&& debconf-show debconf
# Install Packages
RUN set -x \
&& mv /etc/apt/apt.conf.d/70debconf . \
&& ${APT} update \
&& ${APT} install apt-utils >/dev/null \
&& mv 70debconf /etc/apt/apt.conf.d \
&& ${APT} upgrade >/dev/null \
&& ${APT} install curl >/dev/nullReferences: |
|
Thank you @stephanwehr for your insight! :) |
|
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
|
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
|
in the end the reco from @stephanwehr is enough: |
This. This is exactly what I was looking for. |
|
Even after adding I still get this for the install of apt-utils: Notice that it still produces the warning: However this warning only appears for the install of apt-utils, and additional warnings do not show up for installs of other packages after this initial warning |
Simplest answer, the nasty warning is finally gone |
[16.04] debconf: delaying package configuration, since apt-utils is not installed #319: phusion/baseimage-docker#319
and others
On newest image 0.9.19, if I run any apt-get command, I received the following red warning line:
debconf: delaying package configuration, since apt-utils is not installedMinimal example:
This is only happening in 0.9.19 / Ubuntu 16.04.
The text was updated successfully, but these errors were encountered: