CarrierReleaser2024, whenever I am within the RosBELin2.2.1 I do have no name anymore, but outside of RosBE it is ok

This problem is no blocker for *branching* the 0.4.15-release.
But it is an inconvenience, and therefore I would appreciate if we could fix it during RC-phase before we will release to the public (aka. turning the big-blue-download-button on our homepage to point to 0.4.15)

Problem:
Whenever I do log on to carrier-releaser2024, I do
initially have the proper login name
but as soon as I do start the RosBE, my user name is gone.

It is restored as soon as I do leave the RosBE.

That makes working on the cr2024 more time-consuming, because I do have to switch into and out of RosBE multiple times, and have to change the working directory several times during the iso-creation-process.
E.g. I can't upload to sourceforge without having a username.

This problem did not happen on the old carrier-releaser that we used "from 2017 up to now" for 0.4.7 to 0.4.14.

It might be related to the docker-stuff. But I do hope that we can somehow overcome it, since it happens only while being within RosBE-Linux2.2.1