Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.04] debconf: delaying package configuration, since apt-utils is not installed #319

Open
hyperknot opened this issue Jul 14, 2016 · 50 comments
Assignees
Labels
Milestone

Comments

@hyperknot
Copy link
Collaborator

@hyperknot hyperknot commented Jul 14, 2016

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:

FROM phusion/baseimage:0.9.19

# Use baseimage-docker's init system.
CMD ["/sbin/my_init"]

# ...put your own build instructions here...
RUN apt-get update && apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# Clean up APT when done.
RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

This is only happening in 0.9.19 / Ubuntu 16.04.

@hyperknot hyperknot changed the title debconf: delaying package configuration, since apt-utils is not installed 16.04: debconf: delaying package configuration, since apt-utils is not installed Jul 14, 2016
@hyperknot hyperknot changed the title 16.04: debconf: delaying package configuration, since apt-utils is not installed [16.04] debconf: delaying package configuration, since apt-utils is not installed Jul 14, 2016
@FranklinYu
Copy link

@FranklinYu FranklinYu commented Aug 2, 2016

Upstream problem; I can confirm this with clean image ubuntu:16.04. Reporting to them at tianon/docker-brew-ubuntu-core#59.

@aa21
Copy link

@aa21 aa21 commented Sep 8, 2016

Did you find any solutions for this? @hyperknot @FranklinYu

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Sep 8, 2016

yes, I'm installing it myself

On Thursday, 8 September 2016, aa notifications@github.com wrote:

Did you find any solutions for this? @hyperknot
https://github.com/hyperknot @FranklinYu https://github.com/franklinyu


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/AAeKj3pTbewfwizfVv8RAwaA58N22DN7ks5qn5TUgaJpZM4JMfSU
.

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Sep 8, 2016

@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.

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Sep 9, 2016

My solution is just to put a

RUN apt-get update && apt-get install -y --no-install-recommends apt-utils

line in the docker file and it fixes the problem.

@aa21
Copy link

@aa21 aa21 commented Sep 13, 2016

Thanks @hyperknot and @FranklinYu.

@WesleyBatista
Copy link

@WesleyBatista WesleyBatista commented Oct 21, 2016

It did not worked for me =/

Step 2 : ENV DEBIAN_FRONTEND noninteractive
 ---> Running in 1b35b989ce4d
 ---> 78f654f9ea69
Removing intermediate container 1b35b989ce4d
Step 3 : RUN apt-get update && apt-get install -y --no-install-recommends apt-utils
 ---> Running in 29d7eb2e1bb5
Get:1 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [95.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/main Sources [1103 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [5179 B]
Get:6 http://archive.ubuntu.com/ubuntu xenial/universe Sources [9802 kB]
Get:6 http://archive.ubuntu.com/ubuntu xenial/universe Sources [9802 kB]
Get:7 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1558 kB]
Get:8 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [14.1 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [9827 kB]
Get:10 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [250 kB]
Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [129 kB]
Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [522 kB]
Get:13 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [432 kB]
Get:14 http://archive.ubuntu.com/ubuntu xenial-security/main Sources [52.7 kB]
Get:15 http://archive.ubuntu.com/ubuntu xenial-security/universe Sources [13.4 kB]
Get:16 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages [196 kB]
Get:17 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [62.2 kB]
Fetched 18.4 MB in 4min 14s (72.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
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 5 not upgraded.
Need to get 251 kB of archives.
After this operation, 1203 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libapt-inst2.0 amd64 1.2.12~ubuntu16.04.1 [55.4 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 apt-utils amd64 1.2.12~ubuntu16.04.1 [196 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 251 kB in 1s (176 kB/s)
Selecting previously unselected package libapt-inst2.0:amd64.
(Reading database ... 7256 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.2.12~ubuntu16.04.1_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.2.12~ubuntu16.04.1) ...
Selecting previously unselected package apt-utils.
Preparing to unpack .../apt-utils_1.2.12~ubuntu16.04.1_amd64.deb ...
Unpacking apt-utils (1.2.12~ubuntu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libapt-inst2.0:amd64 (1.2.12~ubuntu16.04.1) ...
Setting up apt-utils (1.2.12~ubuntu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
@Lewiscowles1986
Copy link

@Lewiscowles1986 Lewiscowles1986 commented Oct 31, 2016

it's the only red command I now get when setting up my jekyll x86 base image...

@yosualb
Copy link

@yosualb yosualb commented Nov 23, 2016

RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends apt-utils

didn't work for me too.

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Nov 24, 2016

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.

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Nov 24, 2016

I started making an updated fork of this project, containing Ubuntu 16.04 fixes, including this one. Have a look here:
https://github.com/hyperknot/baseimage16

@vlymar
Copy link

@vlymar vlymar commented Jan 13, 2017

The command does get installed, and following apt-get commands do not show any error / warning messages.

When I install apt-utils before the rest of apt packages, I only get delaying package configuration for the installation of the apt-utils package, which makes sense. However, I get the following warnings for the other packages:

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
dpkg-preconfigure: unable to re-open stdin: 

Apparently this is also a harmless warning that can be avoided by setting DEBIAN_FRONTEND=noninteractive as some others have in this thread.

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 ENV to set this because it will persist in the image, but you only want that value set during the docker build stage.

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?

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Jan 13, 2017

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

ENV DEBIAN_FRONTEND noninteractive

in the beginning of the Docker file
and I set

ENV DEBIAN_FRONTEND teletype

At the very end. This way both interactive and non-interactive modes get set.

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Jan 16, 2017

@hyperknot Why two ENV instead of a single (and more future-proof) ARG?

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Jan 16, 2017

They are totally different. ENV is persistent in the image. It'd still need two cases here.

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Jan 16, 2017

But why do you need to persist it (which overrides the default)? The default frontend works for me. In addition, --no-install-recommends can be omitted since apt-utils doesn't have any recommended package.

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Jan 16, 2017

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Jan 16, 2017

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 (??); the newt, mentioned as default in documentation, still produces the warning for me (???).

@hyperknot
Copy link
Collaborator Author

@hyperknot hyperknot commented Jan 16, 2017

@Theaxiom
Copy link
Collaborator

@Theaxiom Theaxiom commented Mar 19, 2017

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.

@Theaxiom Theaxiom closed this Mar 19, 2017
@aairey
Copy link

@aairey aairey commented Apr 23, 2017

FWIW
It is better to use ARG on newer docker installations, as this only sets the ENV during build time (See moby/moby#4032).

ARG DEBIAN_FRONTEND=noninteractive

But I am still getting the warnings about apt-utils.

@Theaxiom
Copy link
Collaborator

@Theaxiom Theaxiom commented Apr 23, 2017

@aairey Did you try adding this to your Dockerfile?

RUN apt-get update && apt-get install -y --no-install-recommends apt-utils

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Apr 24, 2017

@aairey We discussed about why we need ENV instead of ARG above.

@aairey
Copy link

@aairey aairey commented Apr 24, 2017

@Theaxiom this just installs apt-utils?
I thought there was a way to just make the warning go away without installing apt-utils.
When apt-utils is installed, the build is way slower, and since it is not the default I prefer not to install it.
But seems there is no way to get rid of the warning without installing apt-utils?

@FranklinYu it works for me just using ARG.
The apt-utils warning and reason for using noninteractive is unrelated. (unless I am missing something?).
The noninteractive setting just makes sure no dialogs are opened and that dpkg-reconfigure dus not prompt you for input.
At least that is my understanding after fiddling around with it yesterday.
And thus you should always use noninteractive when using apt-get during build.

@Theaxiom
Copy link
Collaborator

@Theaxiom Theaxiom commented Apr 24, 2017

@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.

@k41n3w
Copy link

@k41n3w k41n3w commented Feb 1, 2019

@Theaxiom I'd definitely add apt-utils here:
https://github.com/hyperknot/baseimage16/blob/master/image/prepare.sh#L34
and teletype at the end:
https://github.com/hyperknot/baseimage16/blob/master/image/Dockerfile#L19

noninteractive is already part of buildconfig

Add the ENV DEBIAN_FRONTEND teletype on my dockerfile works for me. Thanks

@Lucas-Malor
Copy link

@Lucas-Malor Lucas-Malor commented Jun 18, 2019

teletype does not work for me. Neither installing apt-utils This is my Dockerfile:

FROM ubuntu:18.04
ENV DEBIAN_FRONTEND=teletype

RUN apt-get update
RUN apt-get install -y --no-install-recommends apt-utils
RUN apt-get install -y evince

CMD ["evince"]
@spartacutz
Copy link

@spartacutz spartacutz commented Jul 5, 2019

I found this solution from:
https://stackoverflow.com/questions/51023312/docker-having-issues-installing-apt-utils

it consists of following the apt-get install command on the same line as ENV DEBIAN_FRONTEND noninteractive :

DEBIAN_FRONTEND=noninteractive apt-get install -y pkgs...

@zendriani3006
Copy link

@zendriani3006 zendriani3006 commented Jul 27, 2019

my solution

apt-get update && apt-get install -y --no-install-recommends apt-utils

@Marco-Sulla
Copy link

@Marco-Sulla Marco-Sulla commented Jul 27, 2019

teletype does not work for me. Neither installing apt-utils This is my Dockerfile:

FROM ubuntu:18.04
ENV DEBIAN_FRONTEND=teletype

RUN apt-get update
RUN apt-get install -y --no-install-recommends apt-utils
RUN apt-get install -y evince

CMD ["evince"]

@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 ARG DEBIAN_FRONTEND=noninteractive without success

@kingdonb
Copy link
Collaborator

@kingdonb kingdonb commented Jul 28, 2019

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.

@chetabahana
Copy link

@chetabahana chetabahana commented Aug 5, 2019

While the issue has been closed but still unclear solution on this case that already runs for years .

Currently the highest votes goes to:

RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends apt-utils

but it still gives the warning

debconf: delaying package configuration, since apt-utils is not installed
bqstony added a commit to bqstony/zookeeper-docker that referenced this issue Aug 20, 2019
@kingdonb
Copy link
Collaborator

@kingdonb kingdonb commented Aug 23, 2019

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?

@ssbarnea
Copy link

@ssbarnea ssbarnea commented Oct 20, 2019

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.

@bjornoj
Copy link

@bjornoj bjornoj commented Dec 11, 2019

I don't get why this issue is closed, it is still an issue. This is my Dockerfile:

FROM postgres:latest

ENV TZ=UTC
ENV DEBIAN_FRONTEND=noninteractive
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone
RUN apt-get update
RUN apt-get install -y --no-install-recommends apt-utils
RUN apt-get install -y postgresql-contrib
COPY sql/* /docker-entrypoint-initdb.d/

And these are my logs, from running docker-compose build

Step 5/8 : RUN apt-get update
 ---> Running in 142bd8adbec2
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [161 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7,908 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [5,792 B]
Get:7 http://apt.postgresql.org/pub/repos/apt buster-pgdg InRelease [46.2 kB]
Get:8 http://apt.postgresql.org/pub/repos/apt buster-pgdg/main amd64 Packages [151 kB]
Get:9 http://apt.postgresql.org/pub/repos/apt buster-pgdg/12 amd64 Packages [861 B]
Fetched 8,510 kB in 6s (1,437 kB/s)
Reading package lists...
Removing intermediate container 142bd8adbec2
 ---> 7024764329ca
Step 6/8 : RUN apt-get install -y --no-install-recommends apt-utils
 ---> Running in f9258fb99c3f
Reading package lists...
Building dependency tree...
Reading state information...
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 5 not upgraded.
Need to get 625 kB of archives.
After this operation, 1,655 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 0s (4,284 kB/s)
Selecting previously unselected package libapt-inst2.0:amd64.
(Reading database ... 13981 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 f9258fb99c3f
 ---> 1fa9de755ff2
@scrlkx
Copy link

@scrlkx scrlkx commented Dec 31, 2019

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
@Marco-Sulla
Copy link

@Marco-Sulla Marco-Sulla commented Dec 31, 2019

@danielxfr It's seems to me correct. The message comes out when you are installing apt-utils itself. Of course debconf does not find apt-utils and gives you the warning, because apt-utils is not yet installed.

But when you later install apt-transport-https, no warning is displayed.

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?

@sebthom
Copy link

@sebthom sebthom commented Jan 12, 2020

@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,...
@Theaxiom
Copy link
Collaborator

@Theaxiom Theaxiom commented Jan 30, 2020

I will reopen this issue until we come to a conclusion.

@Theaxiom Theaxiom reopened this Jan 30, 2020
@alanivey
Copy link

@alanivey alanivey commented Feb 24, 2020

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:

FROM ...

ARG DEBIAN_FRONTEND=noninteractive

SHELL ["/bin/bash", "-c"]

RUN \
  apt-get update -y && \
  apt-get install -y apt-utils 2> >( grep -v 'debconf: delaying package configuration, since apt-utils is not installed' >&2 ) && \
  apt-get install -y --no-install-recommends package1,package2,...
briangleeson added a commit to briangleeson/greenwell-tekton-1 that referenced this issue May 12, 2020
`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)
shmidtelson added a commit to shmidtelson/action-wordpress-plugin-deploy that referenced this issue Sep 5, 2020
@marcusjwhelan
Copy link

@marcusjwhelan marcusjwhelan commented Sep 29, 2020

This is also an issue exists on Ubuntu's 18.04 image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet