)

* discard the sticky disk's resolv-host.conf before buildkitd starts

BuildKit bind-mounts <root>/runc-*/executor/resolv-host.conf into every
--network=host RUN and only regenerates it on the daemon's first container
or when it is older than /etc/resolv.conf (boot time on our VMs). It
deletes hosts and resolv.conf at startup but not this file, so on a sticky
disk it survives from whichever VM last committed, naming that VM's eth0
address as nameserver. Any build whose first container is not the host-mode
RUN (e.g. a # syntax= frontend) then runs host-network steps with a dead
resolver and every lookup fails with EAI_AGAIN.

Remove the file right after mounting the sticky disk so the daemon writes
one with this VM's address.

* build dist for the resolv-host.conf cleanup

* deps: bump axios to 1.20.0 and remove stale package-lock.json

Co-authored-by: Codesmith Staging <[email protected]>

* dist: rebuild with axios 1.20.0

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

---------

Co-authored-by: Codesmith Staging <[email protected]>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Pruned layers keep their RBD extents allocated on the backing store until
the guest discards them. Run a best-effort fstrim on /var/lib/buildkit
before unmount, only when the run is still on track to commit (integrity
check passed, no early deny, no SIGKILL, no failed steps) and only when
the host enabled it: the VM agent returns
GetStickyDiskResponse.fstrim_timeout_secs, saved in action state at mount
time; 0 means no trim. A positive fstrim_min_extent_bytes becomes
`fstrim -m`. Any failure or timeout only logs.

Port of #143 (release/v2) to the v1 line; v1 has no DockerJobLifecycle
report, so the trim result is logged only.

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>