Hi, running mailcow on arm64 (experimental, I know), I noticed that the front page says that the containers were "started on invalid date" - see attached screenshot.[upl-image-preview url=https://community.mailcow.email/assets/files/2024-04-21/1713686276-642954-screenshot-2024-04-21-at-095639.png] FWIW, ``` root@hx2:/opt/mailcow-dockerized# timedatectl Local time: Sun 2024-04-21 09:55:34 CEST Universal time: Sun 2024-04-21 07:55:34 UTC RTC time: Sun 2024-04-21 07:55:34 Time zone: Europe/Luxembourg (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no ``` Regards, -Patrick

Well, if you think it's a bug and you can reproduce it, you should open an [issue](https://github.com/mailcow/mailcow-dockerized/issues). This is just a community forum.

I opened an issue 2 weeks ago: https://github.com/mailcow/mailcow-dockerized/issues/5851. Should I mark this thread as resolved @"D4niel"#88 ?

started on invalid date

BornDeranged

Hi,
running mailcow on arm64 (experimental, I know), I noticed that the front page says that the containers were “started on invalid date” - see attached screenshot.

FWIW,

root@hx2:/opt/mailcow-dockerized# timedatectl
               Local time: Sun 2024-04-21 09:55:34 CEST
           Universal time: Sun 2024-04-21 07:55:34 UTC
                 RTC time: Sun 2024-04-21 07:55:34
                Time zone: Europe/Luxembourg (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Regards,
-Patrick

D4niel

Well, if you think it’s a bug and you can reproduce it, you should open an issue. This is just a community forum.

BornDeranged

It does look like a bug, I was hoping someone also running on arm64 would chime in to confirm.
No such issue seems to be open in Github, but I have to do some checks first before opening an issue.

BornDeranged

I opened an issue 2 weeks ago: mailcow/mailcow-dockerizedissues/5851.
Should I mark this thread as resolved @D4niel ?