Warning shows up in mismatch version in aarch64

[mathric]

When trying to run docker in version 4.4 or 4.2. The following error shows up
pull the image using sha256:1f597c605bdc2a244e7b58ab9f14abcadf4905c2efe6dbf7b21e7b7267e3bbd1 also have same result.

but it doesn't shows up when run in version 3.6

---

The following is the cpu and distro info

[yosifkit]

This applies the warning across all versions, with the justification that affected users might want to know sooner than post-5.0-upgrade that their containers will not be starting successfully.

- #491 (and the follow up for arm64v8 #511)

3.6 is no longer a supported release, so it did not get the warning message. The warning message is there to let you know that newer versions will likely not work on your host CPU architecture (see the provided links); it is not an error. Your listed processor is a Cortex-A72 and according to the "List of ARM Processors", it is an ARMv8-A which means it is not ARMv8.2-A or higher and so it is being correctly detected as unable to run MongoDB 5.0+.

Here is the detection code:

mongo/docker-entrypoint.sh

Lines 40 to 52 in 4bde9c8

	arm64) # https://github.com/docker-library/mongo/issues/485#issuecomment-970864306
	# https://en.wikichip.org/wiki/arm/armv8#ARMv8_Extensions_and_Processor_Features
	# http://javathunderx.blogspot.com/2018/11/cheat-sheet-for-cpuinfo-features-on.html
	if ! grep -qE '^Features.* (fphp|dcpop|sha3|sm3|sm4|asimddp|sha512|sve)( .*|$)' /proc/cpuinfo; then
	{
	echo
	echo 'WARNING: MongoDB 5.0+ requires ARMv8.2-A or higher, and your current system does not appear to implement any of the common features for that!'
	echo ' see https://jira.mongodb.org/browse/SERVER-55178'
	echo ' see also https://en.wikichip.org/wiki/arm/armv8#ARMv8_Extensions_and_Processor_Features'
	echo ' see also https://github.com/docker-library/mongo/issues/485#issuecomment-970864306'
	echo
	} >&2
	fi

[mathric]

Thanks for the reply. Since the container also stop immediately after start up I thought it wasn't just warning and it's about why the container stop.
So I think the issue will become the container can't start in version 4.4 or 4.2 in that environment without other error message.

Update:
I use inspect to look the container, the exit code was 132

[yosifkit]

It seems that the minimum has increased for older versions now too: https://jira.mongodb.org/browse/SERVER-71772 😞. Seems not great for them to do this on older releases.

[mathric]

okey, thanks for the help. Will try to get another enviroment for this.