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
TODO: need to cross-check that there is no way the
SeBackupPrivilege can be abused/exploited.
WIP: how best to handle the files to be exclused
without touching `fsutil` - see moby#5011
Signed-off-by: Anthony Nandaa <profnandaa@gmail.com>
Exporting via buildctl v0.14.1 (and not via remote builder node in Docker Desktop v4.31.1) does indeed work in this example as well as in my own project.
Would it be possible to not include system files when using scratch as a base for artifacts target to match Linux experience?
This is as a follow-up of #4994
Need to find the best way of excluding these files in the export, without touching
fsutil
iself.Here is the change when you change from
fsutil
instead:Sure, I can add that the exclusion, the team was okay with skipping that, was listed among what's skipped in their layer exports:
Do you suggest adding that in the
fsutil
side or sending it from the caller?Originally posted by @profnandaa in #4994 (comment)
The text was updated successfully, but these errors were encountered: