libfaketime is returning correct time instead of returning time(incorrect one) configured. This behaviour was observed on raspberry pi(ARM architecture)

[shivaji506]

reproduction steps on raspberry pi

`FROM debian:12

RUN apt-get update &&
apt-get install -y libfaketime

ENV LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1

ENV FAKETIME="-10m"`

Build image using above file(assume image tag as faketime1) and ran the container as shown below
docker run --rm -it --name testContainer1 faketime1 date -> returning correct time eventhough we configured as 10min delay through FAKETIME

similar behaviour observed in image built on debian:latest base image.

`FROM debian:11

RUN apt-get update &&
apt-get install -y libfaketime

ENV LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1

ENV FAKETIME="-10m"`

Build image using above file(assume image tag as faketime2) and ran the container as shown below
docker run --rm -it --name testContainer2 faketime2 date -> returning configured faketime correctly. If current time is 'T', it is returning 'T-10minutes' which is expected one. Tried same with debain:10 base image. It's working as expected. Not sure something wrong from 12 version.

PS: I also tried all the above scenarios on x86_64 machine containers(ubuntu laptop) with appropriate LD_PRELOAD path. Didn't faced any issues. date calls returning configured faketime properly.