google/gvisor: runsc/container/state_file.go; 8 LoC

Found a possible issue in [google/gvisor](https://www.github.com/google/gvisor) at [runsc/container/state_file.go](https://github.com/google/gvisor/blob/85c1c3ed4b8d32c499c53917765acef20cb16248/runsc/container/state_file.go#L174-L181)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to id is reassigned at line 179

[Click here to see the code in its original context.](https://github.com/google/gvisor/blob/85c1c3ed4b8d32c499c53917765acef20cb16248/runsc/container/state_file.go#L174-L181)

Click here to show the 8 line(s) of Go which triggered the analyzer.

```go
for _, id := range ids {
if strings.HasPrefix(id.ContainerID, partialID) {
if rv != nil {
return FullID{}, fmt.Errorf("id %q is ambiguous and could refer to multiple containers: %q, %q", partialID, rv, id)
}
rv = &id
}
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 85c1c3ed4b8d32c499c53917765acef20cb16248

Start with runsc/container/state_file.go around lines 174-181 and read the surrounding lookup logic. Check whether taking a pointer to the range-loop variable can change the selected container or error behavior, then use a reaction to classify the finding as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.