[16.04] debconf: delaying package configuration, since apt-utils is not installed #319
Comments
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. |
Add the ENV DEBIAN_FRONTEND teletype on my dockerfile works for me. Thanks |
|
I found this solution from: it consists of following the
|
my solution apt-get update && apt-get install -y --no-install-recommends apt-utils |
@spartacutz @zendriani3006 I already tried your suggestions and they does not work for me. Furthermore they are already suggested in this issue. I also tried |
There should be no difference between runtime environments in a container on one host to another, I don't know why something would work for one person but not others unless there was drift over time. Please provide us with some error output, if you think something is wrong. |
While the issue has been closed but still unclear solution on this case that already runs for years . Currently the highest votes goes to:
but it still gives the warning
|
I am assuming you get this message while installing apt-utils, indicating that apt-utils hasn't finished installing yet, but that subsequent apt-get install invocations no longer print the warning. Is that not the case? |
I am quite curious if someone manages to result the apt-utils issue without triggering any warnings. Ignoring warnings in builds is very bad practice, once you let them in, they will grow exponentially and everyone will ignore them. |
I don't get why this issue is closed, it is still an issue. This is my Dockerfile:
And these are my logs, from running
|
I keep having the same issue. Nothing said above solved my problem. Where we are going? My Dockerfile: FROM php:7.2-apache
ARG TERM=xterm
ARG LC_ALL=C.UTF-8
ARG DEBIAN_FRONTEND=noninteractive
RUN apt-get update
RUN apt-get install --yes --no-install-recommends apt-utils
RUN apt-get install --yes --no-install-recommends apt-transport-https My output: Sending build context to Docker daemon 2.048kB
Step 1/7 : FROM php:7.2-apache
---> d0e98d20a124
Step 2/7 : ARG TERM=xterm
---> Running in e2c44669cea7
Removing intermediate container e2c44669cea7
---> 2f2ace91ade4
Step 3/7 : ARG LC_ALL=C.UTF-8
---> Running in 2f63d8e4765f
Removing intermediate container 2f63d8e4765f
---> cbbdc3930308
Step 4/7 : ARG DEBIAN_FRONTEND=noninteractive
---> Running in 7a9d5fd0474c
Removing intermediate container 7a9d5fd0474c
---> 9b41b58bd730
Step 5/7 : RUN apt-get update
---> Running in 40244a45a5fb
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security-cdn.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Get:4 http://deb.debian.org/debian buster/main amd64 Packages [7908 kB]
Get:5 http://security-cdn.debian.org/debian-security buster/updates/main amd64 Packages [167 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [5792 B]
Fetched 8317 kB in 9s (897 kB/s)
Reading package lists...
Removing intermediate container 40244a45a5fb
---> 1ac1a52a0771
Step 6/7 : RUN apt-get install --yes --no-install-recommends apt-utils
---> Running in 843eb4e89040
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
sensible-utils
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
libapt-inst2.0
The following NEW packages will be installed:
apt-utils libapt-inst2.0
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 625 kB of archives.
After this operation, 1655 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 libapt-inst2.0 amd64 1.8.2 [204 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 apt-utils amd64 1.8.2 [421 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 625 kB in 1s (692 kB/s)
Selecting previously unselected package libapt-inst2.0:amd64.
(Reading database ... 13530 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.8.2_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.8.2) ...
Selecting previously unselected package apt-utils.
Preparing to unpack .../apt-utils_1.8.2_amd64.deb ...
Unpacking apt-utils (1.8.2) ...
Setting up libapt-inst2.0:amd64 (1.8.2) ...
Setting up apt-utils (1.8.2) ...
Processing triggers for libc-bin (2.28-10) ...
Removing intermediate container 843eb4e89040
---> cacb6cd31c49
Step 7/7 : RUN apt-get install --yes --no-install-recommends apt-transport-https
---> Running in 46e69d0a1858
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
sensible-utils
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
apt-transport-https
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 149 kB of archives.
After this operation, 156 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 apt-transport-https all 1.8.2 [149 kB]
Fetched 149 kB in 0s (377 kB/s)
Selecting previously unselected package apt-transport-https.
(Reading database ... 13660 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_1.8.2_all.deb ...
Unpacking apt-transport-https (1.8.2) ...
Setting up apt-transport-https (1.8.2) ...
Removing intermediate container 46e69d0a1858
---> 0d811308b11d
Successfully built 0d811308b11d |
@danielxfr It's seems to me correct. The message comes out when you are installing But when you later install PS: I continue to receive notification from this bug even if I unsubscribed... now I subscribe and re-unsubscribe, but if the problem persist, where can I signal it? |
@Marco-Sulla I think it’s https://support.github.com/contact |
@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 |
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 installed
Minimal example:
This is only happening in 0.9.19 / Ubuntu 16.04.
The text was updated successfully, but these errors were encountered: