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
When using py3_image the mtime (modification time) for all the files are set to 0 unix time (cira 1970). Some python libraries panic when they see that (eg. zipfile python builtin lib ValueError: ZIP does not support timestamps before 1980)
Describe the solution you'd like
container_image has an option to set all mtimes to a fixed valued: see portable_mtime but IIUC it needs to be routed to py3_image through the signatures somehow, hence this feature request.
Basically can we by default or through an option in py3_image set all the mtimes to something other than 0 ?
The text was updated successfully, but these errors were encountered:
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!
🚀 feature request
Description
When using
py3_image
the mtime (modification time) for all the files are set to 0 unix time (cira 1970). Some python libraries panic when they see that (eg.zipfile
python builtin libValueError: ZIP does not support timestamps before 1980
)Describe the solution you'd like
container_image
has an option to set all mtimes to a fixed valued: seeportable_mtime
but IIUC it needs to be routed topy3_image
through the signatures somehow, hence this feature request.Basically can we by default or through an option in
py3_image
set all the mtimes to something other than0
?The text was updated successfully, but these errors were encountered: