#IIRC buildkit only invalidated the cache
1 messages · Page 1 of 1 (latest)
@wintry lantern just to double-check, the issue is that this file is causing invalidations even though the contents aren't actually changing? One (surprising) thing is that when it comes to mounts, BuildKit will only enable content-based hashing when the mount is readonly. Depends on your exact circumstance, but we do expose a readonly option for mounts so that is likely possible. Is that the only time you are seeing invalidations? Or are you also getting invalidations in other scenarios?
i haven't nailed it all down yet, i was about to go through a phase of tracking down all unexpected invalidations and then one popped up quickly, so i'll do more testing
particularly with read-only, if read-only is ensuring only checksum checks
anyone have an example github actions workflow that runs dagger via arm64 arch ?
not using a self-hosted arm64 runner