New answers tagged

1

Finally found why in the HACKS chapter on this page : https://manpages.debian.org/buster/debconf-doc/debconf-devel.7.en.html Debconf is currently not fully integrated into dpkg (but I want to change this in the future), and so some messy hacks are currently called for. You need to call the debconf library at the beginning of your postinst script, using ...


2

One way to deal with this is to tell debconf to not ask questions. You could do this for example via: RUN DEBIAN_FRONTEND=noninteractive apt-get install ... RUN export DEBIAN_FRONTEND=noninteractive && ... ARG DEBIAN_FRONTEND=noninteractive Please note: Don't use ENV to set this variable, as it would persist in the final image, which is probably ...


3

The workaround I found for gitlab-runner is to manually create a 'gitlab-runner' user with a specified local home directory.


0

There is also the --debug option for dpkg, as in sudo dpkg --debug=72200 -i package.deb There are several available options for verbose output and they can be combined. You can see all available options by running: dpkg --debug=help. pi@kaldi:~ $ dpkg --debug=help dpkg debugging option, --debug=<octal> or -D<octal>: Number Ref. in source ...


0

I ran into a similar issue trying to run my script in crontab. I was automating updates using apt-get update in my script. I need to add the path found with the command $PATH to my script under: #!/bin/bash PATH=/usr/lib64/ccache:usr/local/bin:/bin:/usr/local/sbin:/usr/sbin:home/learner2/.local/bin:/home/learner2/bin apt-get -y update ...


1

I have run into this as well on a script that previously worked fine. This is due to a Mono upgrade from 5.18.0.x to 6.0.0 which was recently released (July 14th, 2019). I was able to reproduce the error with both NuGet 4.7.0.5148 (on OSX) and 5.1.0.6013 (on Ubuntu 18.04). After managing to downgrade Mono to 5.18.1 on my Mac the script worked again. Am ...


Top 50 recent answers are included