Ananth
We'll need a migration path as well right? It's not just adding support for v2 policies.
So if v2 support were added, new homes would default to v2 policy while existing ones with v1 would continue as is?
Yep, that's included. The [README](https://github.com/GoogleContainerTools/distroless/blob/main/base/README.md) for the base image mentions this, and I've personally used them before.
Could it have something to do with my user account being created by systemd-homed?
This looks right @Avemark. I don't have an Arch install to confirm just yet, but if your user is using systemd-homed, then it should be it.
If multiple goroutines are writing to the output in parallel, will the output file have gaps in between partially written chunks? If so, how would resuming a partial download work?
Yep that makes sense @justinfx.
What happens if grab crashes before it can truncate the file? If you only wrote completed chunks to the file, then you wouldn't need to truncate it in the first...
Yeah in-memory buffers alone won't be enough to cover, say large chunk sizes or many parallel chunks. I've been toying with the idea of an in-memory buffer that spills over...
Also @ndrewnee would you mind adding a `MustProcessWithOptions` func too?