@diemol - my assumed fix didn't work for setting the language env variable in the binary wrapper of the selenium docker project - it set the value in the node container, but the dynamically created containers still have the default locale (en-US).

My gut is telling me this is a better, more reliable approach and is akin to the way the timezone is able to be set/overridden.

Any feedback would be much appreciated as this is very new to me.

OK, so it worked when you used it in standalone mode but not in Dynamic. How did you start the Standalone mode and how did you start the test?

So... I realised after re-testing why it wasn't working after the release that it was because I was setting environment variables in the ansible script I was using for deploying the node containers for LANGUAGE (and LANG and LC_ALL) (hence the env variables were as expected!), so made a rookie error QA-ing, despite being a QA-er! Apologies.

So... I realised after re-testing why it wasn't working after the release that it was because I was setting environment variables in the ansible script I was using for deploying the node containers for LANGUAGE (and LANG and LC_ALL) (hence the env variables were as expected!), so made a rookie error QA-ing, despite being a QA-er! Apologies.

Sorry, I am not following. Does it mean it is working now?

No - in short, my previous fix didn't work.

Looking at how the dynamic grid creates the node containers, though, I thought this would be a more suitable place to change how the environment variables are set. (I think this is how the dynamic node containers are generated)

@jsa34 I made the change where you suggested it, thank you for digging into it and giving pointers where to fix it. Now the parent container will use its LANGUAGE env var to set the language in the child ones.

I thought about having it as a capability but this use case is not common and creates more maintenance.