Dbms.allow_upgrade usage in a container

Hi,

i try to upgrade an old neo4j dump that i received from a colleague.
It appears to be from a 4.0.x version, and my plan is now to load and migrate the data into a 4.4.x version and afterwards with a 5.x version.

I am on a Windows host and use docker containers to run Neo4J.

I added NEO4J_dbms_allow__upgrade=true to the Docker envs, and i can see the line dbms.allow_upgrade=true if i check cat /var/lib/neo4j/conf/neo4j.conf in the running container.

However, when i actually try to load the dump, i get this
Selecting JVM - Version:11.0.22+7, Name:OpenJDK 64-Bit Server VM, Vendor:Eclipse Adoptium Done: 69 files, 375.0MiB processed. The loaded database is not on the latest format (current:SF4.0.0, latest:SF4.3.0). Set dbms.allow_upgrade=true to enable migration.

What could be the issue here?

P.S.
running neo4j:4.4.32-enterprise image
P.P.S.
What i also noticed is that this parameter is NOT listed here: Docker specific configuration settings - Operations Manual so maybe that's the problem? But nevertheless, it showed up correctly in the conf file, so in theory it should work, right?