Node Feature Discovery build fails in hermetic mode due to non-deterministic binary path handling in Dockerfile. The build uses "go install" command which places binaries in unpredictable GOPATH locations, and the Dockerfile copies from multiple inconsistent paths causing binary path conflicts.
  

  OpenShift Container Platform 4.19+
  node-feature-discovery component across all affected versions
  

  Always - when building node-feature-discovery in hermetic mode
  

  1. Build node-feature-discovery container in hermetic mode
  2. Dockerfile copies binaries from multiple paths: /go/bin/* and /go/node-feature-discovery/bin/*
  3. "go install" command places binaries in non-deterministic GOPATH locations during hermetic build process
  

  Build fails because binaries are placed in unpredictable locations by "go install" and Dockerfile attempts to copy from multiple conflicting paths

  Error: Inconsistent binary placement causing copy failures during Docker image build process when switching from "go install" to "go build" in
  hermetic mode
  

  Build succeeds using deterministic binary paths. Should use "go build" with explicit output paths instead of "go install" and copy binaries from single consistent location in Dockerfile.
  

  Root cause: "go install" command places binaries in GOPATH-dependent locations that are not deterministic in hermetic builds, unlike "go build"
   which allows explicit output path control.

  Fix implemented: Remove redundant /go/bin/* copy command from Dockerfile and keep only the specific /go/node-feature-discovery/bin/* path. This
   ensures consistent binary placement and eliminates path conflicts during hermetic builds.

  Reference upstream work: https://github.com/openshift/node-feature-discovery/pull/163/changes
  Related hermetic conversion tracking: ART-14586