Current Stable (Mar 26, 2025 at 1:05 am) docker image is not working

[mrforsythexeter]

Branch

On which branch did you notice this bug?

• stable
• release-candidate
• develop

Description

I had a container update using watchtower, now the log only shows

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
    wishthis/wishthis#1) Respect the privacy of others.
    wishthis/wishthis#2) Think before you type.
    wishthis/wishthis#3) With great power comes great responsibility.
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

[mrforsythexeter]

Ignore this, I have no idea what happened, but I have removed the container and image and re-setup, and it appears to be working fine, so happy for you to close if you are not seeing other issues.

[mrforsythexeter]

Actually sorry, its come straight back (was trying to add an item).. same error on repeat.

[Hiobi]

Hi !

Thanks for report, I look at it quickly.

I remove user from sudoer in entrypoint.sh To prevent certain security problems.
Maybe @grandeljay can explain why sudo is required at this point?

[mrforsythexeter]

I do have it running again, I am not 100% sure why it failed, It as my other containers had no problems. However it is back up, and adding items thank you. I just created it again. If there is anything you want me to test or try, please let me know.

[grandeljay]

Maybe @grandeljay can explain why sudo is required at this point?

I dont recognise any of the output here, It's not part of wishthis

[mrforsythexeter]

I would agree its most likley related to the entrypoint.sh.. I notice the build file is using 'php:8.2-apache-bullseye' is it possible the bullseye version was updated and now sudo is throwing this message. of course entry point is using "set -e" as well, so if anything fails, the container will restart.

I guess for some of the commands in there, why would the user www-data be in there? it should have been removed or changed during the build, rather than entrypoint.

But by no means am I a docker expert only just getting to build my own build files now, so I will take other peoples advice.

I maybe do, still have the image, but I am not sure if that helps anyone at this stage, or what you can do with it.

[Hiobi]

Thanks @grandeljay and @mrforsythexeter, agreed

Yeah, it's totally related to entrypoint.sh and how are managed user/group.
I should remove set -e to avoid this issue, as a quick patch.
www-data is set in Dockerfile (build) to prevent container to start with root.
So, sudo is required to set hostname and launch sendmail service.

Maybe, do you have suggestion or PR @mrforsythexeter to improve Dockerfile / entrpypoint.sh ?

[mrforsythexeter]

I don't have a PR at the moment, but I could look at this, we could maybe consider

• Use supervisord
• don't have an MTA local and allow the user to specify the ENV for the mailer to use, and make sure the app accepts these ENV vars (using a common email lib)