and doesn’t show any other events (incoming emails, rejected emails, …).
I’ve encountered some issues with custom postfix settings (which worked flawlessly prior to recent update) and need to debug, which is difficult without logs.
I do see the same errors warnings but Postfix is happily running and accepting mails after that.
Sometimes the logs don’t seem to flush immediately so you might need to wait for a while before you get some output. But that’s unrelated to the warnings.
which worked perfectly before the upgrade (uses regex rules to reject spammers). The real issue is that with this setting enabled, postfix starts rejecting all incoming email, but I can’t see why from the logs!
A while maybe, but it’s been hours and still nothing in logs (neither accepted nor rejected emails are shown, and there is inbound traffic).
followed by a single line of log entries, and ending with the <HEAD> repeated six more times:
<HEAD>
Single line of log entries without line breaks..............................................................................................................................................................................................
<HEAD>
<HEAD>
<HEAD>
<HEAD>
<HEAD>
<HEAD>
I was only looking at the end of the output, and there was always seemingly just the <HEAD> without any other entries.
Definitely something wrong with the rendering of the log via ./launcher logs mail-receiver.
A little convoluted… but I think this should work:
# First, make sure you've got the latest base image locally
docker pull discourse/mail-receiver:release
# Get the top layer of the base image
BASE_IMAGE_HASH=$(docker history discourse/mail-receiver:release -q | head -n 1)
# Get the layers of the **running** version
RUNNING_IMAGE_HASH=$(docker container inspect mail-receiver -f "{{.Image}}")
RUNNING_IMAGE_LAYERS=$(docker history $RUNNING_IMAGE_HASH -q)
# Check if the running image layers include the current base image:
[[ "$RUNNING_IMAGE_LAYERS" == *"$BASE_IMAGE_HASH"* ]] && echo "Up to date"
That will print “Up to date” if you’re up to date. Otherwise, the final line will print nothing, and exit with a non-zero status.
Oh. That’s brilliant. And looks like it’s a general solution that I have previously found only one-off solutions for. It would have taken me a while to figure that out. The RUNNING_IMAGE_LAYERS is what I didn’t know to look for.
I tested it on an instance that had been upgrade and one that hadn’t and it appears to behave as expected.