Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Commit

Permalink
clh: Do not find vsock context ID
Browse files Browse the repository at this point in the history
cloud-hypervisor uses `hybrid vsocks`, it is not needed to find a
context ID.

Fixes: #2481

Signed-off-by: Jose Carlos Venegas Munoz <[email protected]>
  • Loading branch information
jcvenegas committed Feb 19, 2020
1 parent 9f240b2 commit 32196ff
Showing 1 changed file with 3 additions and 7 deletions.
10 changes: 3 additions & 7 deletions virtcontainers/clh.go
Original file line number Diff line number Diff line change
Expand Up @@ -592,14 +592,10 @@ func (clh *cloudHypervisor) generateSocket(id string, useVsock bool) (interface{
clh.Logger().Info("Can't generate socket path for cloud-hypervisor")
return types.HybridVSock{}, err
}
_, cid, err := utils.FindContextID()
if err != nil {
return nil, err
}

return types.HybridVSock{
UdsPath: udsPath,
ContextID: cid,
Port: uint32(vSockPort),
UdsPath: udsPath,
Port: uint32(vSockPort),
}, nil
}

Expand Down

0 comments on commit 32196ff

Please sign in to comment.