Skip to content

Conversation

@AkihiroSuda
Copy link
Member

We can't avoid squashing even after just fixing up whiteout timestamps (#3560 (comment)) ; Squashing is still needed to apply the touch-ed timestamps across multiple RUN instructions.

Squashing will no longer be needed if we can merge:

@tonistiigi
Copy link
Member

@AkihiroSuda Should we add some flag that allows setting timestamp(either to value or to epoch) during COPY in labs channel for v0.12?

@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Jun 30, 2023

@AkihiroSuda Should we add some flag that allows setting timestamp(either to value or to epoch) during COPY in labs channel for v0.12?

👍, but many Dockerfiles will still need squashing

@tonistiigi
Copy link
Member

👍,

Can you send a PR?

@AkihiroSuda
Copy link
Member Author

👍,

Can you send a PR?

Sorry, I'm on PTO and missed this for v0.12

We can't avoid squashing even after just fixing up whiteout timestamps;
Squashing is still needed to apply the `touch`-ed timestamps across multiple `RUN` instructions.

Squashing will no longer be needed if we can merge PR 3560.

Signed-off-by: Akihiro Suda <[email protected]>
@AkihiroSuda AkihiroSuda force-pushed the fix-repro-workarounds-description branch from a3b3c76 to 0758355 Compare July 19, 2023 13:51
@AkihiroSuda AkihiroSuda requested a review from tonistiigi July 19, 2023 13:51
@AkihiroSuda
Copy link
Member Author

ping @tonistiigi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants