I was running a container based on the image
Once I updated the tag/version to
linuxserver/radarr:18.104.22.16807-ls24 the application stopped working.
After debugging a little I noticed that
date behaves weirdly in this image:
$ docker run --rm --entrypoint "" linuxserver/radarr:22.214.171.12407-ls24 date Fri 20 Feb 1970 03:17:15 AM UTC $ docker run --rm --entrypoint "" linuxserver/radarr:126.96.36.19907-ls24 date Sun 01 Mar 1970 09:09:15 AM UTC $ docker run --rm --entrypoint "" linuxserver/radarr:188.8.131.5207-ls24 date Thu 19 Feb 1970 09:04:59 AM UTC
But the old doesn't
$ docker run --rm --entrypoint "" linuxserver/radarr:184.108.40.20695-ls12 date Sat 10 Oct 2020 12:15:09 AM UTC
After meditating for a while, assuming some kind of weird dark magic in the clock, decided to run it with
--privileged for full/raw access
$ docker run --rm --entrypoint "" --privileged linuxserver/radarr:220.127.116.1107-ls24 date Sat 10 Oct 2020 12:16:22 AM UTC
And it worked well (and so did the app, but not important to the question).
I have gone through
docker history of both images but a lot of
RUN curl that might have different results between builds. Still, I don't think anyone (image maintainers) would want to mangle with the date, so it must be something out of their control (no
This is a multi-arch image and these results are from a raspberry Pi (so the arm build of the image). In my amd64 linux laptop, the latest image reports proper
date even without privileged...
What could it be? How can I even start to debug this as I cannot use the