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
{{ message }}
This repository has been archived by the owner on Oct 2, 2023. It is now read-only.
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:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🚀 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: