mirror of
https://github.com/containers/podman.git
synced 2025-08-06 11:32:07 +08:00
642fa98976
This includes two new hidden commands: a 9p server, `podman machine server9p`, and a 9p client, `podman machine client9p` with `server9p` currently only configured to run on Windows and serve 9p via HyperV vsock, and `client9p` only configured to run on Linux. The server is run by `podman machine start` and has the same lifespan as gvproxy (waits for the gvproxy PID to die before shutting down). The client is run inside the VM, also by `podman machine start`, and mounts uses kernel 9p mount code to complete the mount. It's unfortunately not possible to use mount directly without the wrapper; we need to set up the vsock and pass it to mount as an FD. In theory this can be generalized so that the server can run anywhere and over almost any transport, but I haven't done this here as I don't think we have a usecase other than HyperV right now. [NO NEW TESTS NEEDED] This requires changes to Podman in the VM, so we need to wait until a build with this lands in FCOS to test. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
14 lines
690 B
Go
14 lines
690 B
Go
// Package socket provides a low-level network connection type which integrates
|
|
// with Go's runtime network poller to provide asynchronous I/O and deadline
|
|
// support.
|
|
//
|
|
// This package focuses on UNIX-like operating systems which make use of BSD
|
|
// sockets system call APIs. It is meant to be used as a foundation for the
|
|
// creation of operating system-specific socket packages, for socket families
|
|
// such as Linux's AF_NETLINK, AF_PACKET, or AF_VSOCK. This package should not
|
|
// be used directly in end user applications.
|
|
//
|
|
// Any use of package socket should be guarded by build tags, as one would also
|
|
// use when importing the syscall or golang.org/x/sys packages.
|
|
package socket
|