Question - Clarification about the 3.31.2 Image Upgrade Post

There was a post ( Release 3.31.2 (hotfix) ) about the hotfix, which was edited to adjust the tag:

The tag for 3.31.2 is 3.31.2-1

However in the original, when we executed the upgrade, it said:

The tag for 3.31.2 is 3.31.2

This tag worked for us, in that it allowed us to deploy eramba:3.31.2

Was the tag changed to 3.31.2-1, and the post also edited, or is 3.31.2 not contain the hotfix, and 3.31.2-1 contain the hotfix?

TL;DR do I need to shut down eramba, delete docker_app volume, image swap from 3.31.2 to 3.31.2-1? or am I fine on the image that I upgraded to before the edit?

Thanks in advance,

Joel

Hi Joel,

Thanks for asking, and sorry for the confusion caused by the edit.

Both tags contain the PHP security fix:

3.31.2 was released first. We compiled PHP ourselves with the patched version, because the official PHP Docker images with the fix were not available yet at that time.
3.31.2-1 contains exactly the same eramba code, but it is built on the official PHP Docker image (PHP 8.4.27) as soon as it was published.
So the image you already upgraded to is protected and there is no need to do anything urgently. If you want to be on the official PHP image, you can switch to 3.31.2-1 at any time using the same upgrade steps as in the post (stop eramba, remove the docker_app volume, change the image tag to 3.31.2-1 and start it again). Future releases will be built on the official images again.

Thanks for the absolute clarity, and good move doing the manual compile instead of waiting for the docker upstream.

Given that functionally there should be little to no difference, will it be considered a technical blocker to stay on 3.31.2 for future upgrades, i.e. we must image upgrade to 3.31.2-1 before subsequent upgrade? If not, I will move on to other systems and come back to Eramba when we’re looking down the barrel of the 4.0 upgrade (very excited for that btw).

My quasi-educated guess is it’s no issue - most app upgrades (that are done in the admin panel) are basically patching a volume that started life as the docker image you downloaded with the new version. It doesn’t care what image it came from - it could have been 3.10.0, 3.25.5, etc, that have been upgraded X number of times over the years (yes, I know, it’s not the case at the moment due to the manual switch). The image switch procedure effectively deletes the stored app code volume and copies whatever new image you have into a new one to start from.

I suppose the only place you’d have an issue is if one of the upgrades worked with something that’s in the official image vs the manual compile, but I’m guessing that’s highly unlikely.

You don’t necessarily need to switch to 3.31.2-1 the only difference is the PHP image build, but the PHP versions are the same, so you’re all good! And as always, @david.schroth explanation is spot on! :slightly_smiling_face: