Invalid "msmtp" group error in docker by default
lmaxyz opened this issue · 4 comments
lmaxyz commented
Error occurs with chown root:msmtp /etc/msmtprc command execution (16 line in Dockerfile).
Checked with Arch Linux and Debian 11 hosts.
There is another error(or warning) before the first one.
More logs
Get:1 http://deb.debian.org/debian bookworm/main amd64 sensible-utils all 0.0.17+nmu1 [19.0 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 ucf all 3.0043+nmu1 [55.2 kB]
Get:3 http://deb.debian.org/debian bookworm/main amd64 gsasl-common all 2.2.0-1 [182 kB]
Get:4 http://deb.debian.org/debian bookworm/main amd64 libglib2.0-0 amd64 2.74.6-2 [1398 kB]
Get:5 http://deb.debian.org/debian bookworm/main amd64 libglib2.0-data all 2.74.6-2 [1207 kB]
Get:6 http://deb.debian.org/debian bookworm/main amd64 libgssglue1 amd64 0.7-1.1 [20.1 kB]
Get:7 http://deb.debian.org/debian bookworm/main amd64 libidn12 amd64 1.41-1 [83.8 kB]
Get:8 http://deb.debian.org/debian bookworm/main amd64 libntlm0 amd64 1.6-4 [84.8 kB]
Get:9 http://deb.debian.org/debian bookworm/main amd64 libgsasl18 amd64 2.2.0-1 [209 kB]
Get:10 http://deb.debian.org/debian bookworm/main amd64 libsecret-common all 0.20.5-3 [28.5 kB]
Get:11 http://deb.debian.org/debian bookworm/main amd64 libsecret-1-0 amd64 0.20.5-3 [115 kB]
Get:12 http://deb.debian.org/debian bookworm/main amd64 msmtp amd64 1.8.23-1 [201 kB]
Get:13 http://deb.debian.org/debian bookworm/main amd64 shared-mime-info amd64 2.2-1 [729 kB]
Get:14 http://deb.debian.org/debian bookworm/main amd64 xdg-user-dirs amd64 0.18-1 [54.4 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 4387 kB in 0s (29.8 MB/s)
Selecting previously unselected package sensible-utils.
(Reading database ... 14167 files and directories currently installed.)
Preparing to unpack .../00-sensible-utils_0.0.17+nmu1_all.deb ...
Unpacking sensible-utils (0.0.17+nmu1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../01-ucf_3.0043+nmu1_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0043+nmu1) ...
Selecting previously unselected package gsasl-common.
Preparing to unpack .../02-gsasl-common_2.2.0-1_all.deb ...
Unpacking gsasl-common (2.2.0-1) ...
Selecting previously unselected package libglib2.0-0:amd64.
Preparing to unpack .../03-libglib2.0-0_2.74.6-2_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.74.6-2) ...
Selecting previously unselected package libglib2.0-data.
Preparing to unpack .../04-libglib2.0-data_2.74.6-2_all.deb ...
Unpacking libglib2.0-data (2.74.6-2) ...
Selecting previously unselected package libgssglue1:amd64.
Preparing to unpack .../05-libgssglue1_0.7-1.1_amd64.deb ...
Unpacking libgssglue1:amd64 (0.7-1.1) ...
Selecting previously unselected package libidn12:amd64.
Preparing to unpack .../06-libidn12_1.41-1_amd64.deb ...
Unpacking libidn12:amd64 (1.41-1) ...
Selecting previously unselected package libntlm0:amd64.
Preparing to unpack .../07-libntlm0_1.6-4_amd64.deb ...
Unpacking libntlm0:amd64 (1.6-4) ...
Selecting previously unselected package libgsasl18:amd64.
Preparing to unpack .../08-libgsasl18_2.2.0-1_amd64.deb ...
Unpacking libgsasl18:amd64 (2.2.0-1) ...
Selecting previously unselected package libsecret-common.
Preparing to unpack .../09-libsecret-common_0.20.5-3_all.deb ...
Unpacking libsecret-common (0.20.5-3) ...
Selecting previously unselected package libsecret-1-0:amd64.
Preparing to unpack .../10-libsecret-1-0_0.20.5-3_amd64.deb ...
Unpacking libsecret-1-0:amd64 (0.20.5-3) ...
Selecting previously unselected package msmtp.
Preparing to unpack .../11-msmtp_1.8.23-1_amd64.deb ...
Unpacking msmtp (1.8.23-1) ...
Selecting previously unselected package shared-mime-info.
Preparing to unpack .../12-shared-mime-info_2.2-1_amd64.deb ...
Unpacking shared-mime-info (2.2-1) ...
Selecting previously unselected package xdg-user-dirs.
Preparing to unpack .../13-xdg-user-dirs_0.18-1_amd64.deb ...
Unpacking xdg-user-dirs (0.18-1) ...
Setting up xdg-user-dirs (0.18-1) ...
Setting up libglib2.0-0:amd64 (2.74.6-2) ...
No schema files found: doing nothing.
Setting up libglib2.0-data (2.74.6-2) ...
Setting up libntlm0:amd64 (1.6-4) ...
Setting up shared-mime-info (2.2-1) ...
Setting up libidn12:amd64 (1.41-1) ...
Setting up libgssglue1:amd64 (0.7-1.1) ...
Setting up libgsasl18:amd64 (2.2.0-1) ...
Setting up sensible-utils (0.0.17+nmu1) ...
Setting up gsasl-common (2.2.0-1) ...
Setting up libsecret-common (0.20.5-3) ...
Setting up libsecret-1-0:amd64 (0.20.5-3) ...
Setting up ucf (3.0043+nmu1) ...
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 msmtp (1.8.23-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
Configuring msmtp
-----------------
Apparmor is a kernel security mechanism to restrict programs capabilities
with per-program profiles.
.
The AppArmor profile for msmtp covers a lot of common usecases but there are
still corner cases with some options which breaks msmtp with incomprehensible
permissions denied errors.
Enable AppArmor support? [yes/no]
Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111.
Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, <GEN6> line 1.
Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, <GEN6> line 1.
Processing triggers for libc-bin (2.36-9) ...
chown: invalid group: 'root:msmtp'
ssl commented
Thanks for the bug report! I've placed a comment on your pull request to fix this issue.
lmaxyz commented
Hey, @ssl
I think you shouldn't close this issue, because my changes don't resolve it but only let users avoid it.
If someone wants to use mail alerts, they'll still get error.
ssl commented
Hi @lmaxyz, ah I'm sorry I didn't noticed that correctly. I will look into this later. @GlitchWitch could you possibly help with this?
GlitchWitch commented
@ssl Sorry I missed this.
Looking back, this was the change that caused the bug.
The revert done in #140 LGTM as that brings it back to the original state and is what we have internally on our forked repo.