-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last modified date is set to "never" #11916
Comments
Echoing my comment from https://jira.spring.io/browse/SPR-12862, please note that So any Java-based code is unable to differentiate between actual Jan 1, 1970 timestamps and I/O errors. Setting the timestamp one second ahead to Jan 1, 1970, 0:00:01 would help already :-) |
@nwertzberger Can you explain how you managed to create these files? Which filesystem are you using? When I add a file to a container with |
I'm using boot2docker on mac osx. docker info:
docker version:
|
Also, here's my Dockerfile. I am using the ADD tool's functionality for adding tarballs.
|
+1 |
Hello! Mainly:
Then from there, patches/features like this can be re-thought. Hope you can understand. |
I'm not sure if this should be open with you or with every project that decided to sanity-check the last-modified date by comparing it against 0, but it appears that, by default, a docker image will (rightfully?) set the last-modified date of a file to an epoch time of 0.
This makes some amount of sense, but does lead at least spring-core's sanity checker for AbstractResource to freak out. I had to log into the image and modify the image in order to make this go away.
My proposed solution? Honor the last modified dates in the original files, have a way to declare what date i am modifying by, or use the date that Docker built the image at. All of these sound more truthful than saying it happened on Jan 1, 1970.
The text was updated successfully, but these errors were encountered: