You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not really sure if its the right place to report issues related to image itself, however here this image is referenced here a lot, so I assume either you are responsible for image, or at least you can forward to however is.
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!
🐞 bug report
Affected Rule
The issue is caused by the rule:
go_image
Is this a regression?
Not regression
Description
A clear and concise description of the problem...I'm not really sure if its the right place to report issues related to image itself, however here this image is referenced here a lot, so I assume either you are responsible for image, or at least you can forward to however is.
Golang resolves timezones using system files. In case of
@go_image_base//image
file/usr/share/zoneinfo/
is used, and it return wrong date. According to wikipedia Marocco changed it's DST rules in 2018: https://en.wikipedia.org/wiki/Daylight_saving_time_in_MoroccoAccording to https://www.timeanddate.com/time/zone/morocco/casablanca for
2023-04-26
Marocco uses UTC+01, meanwhile go program inside docker container with base as above resolves this date as UTC+00.🔬 Minimal Reproduction
When running file locally correct timezone is printed:
2023-04-26 22:05:00 +0100 +01
However when running it inside docker container using
base = "@go_image_base//image"
wrong timezone is printed:2023-04-26 22:05:00 +0000 +00
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_docker version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: