gvisor/runsc/boot
Nicolas Lacasse 205f1027e6 Refactor the Sandbox package into Sandbox + Container.
This is a necessary prerequisite for supporting multiple containers in a single
sandbox.

All the commands (in cmd package) now call operations on Containers (container
package). When a Container first starts, it will create a Sandbox with the same
ID.

The Sandbox class is now simpler, as it only knows how to create boot/gofer
processes, and how to forward commands into the running boot process.

There are TODOs sprinkled around for additional support for multiple
containers. Most notably, we need to detect when a container is intended to run
in an existing sandbox (by reading the metadata), and then have some way to
signal to the sandbox to start a new container. Other urpc calls into the
sandbox need to pass the container ID, so the sandbox can run the operation on
the given container. These are only half-plummed through right now.

PiperOrigin-RevId: 196688269
Change-Id: I1ecf4abbb9dd8987a53ae509df19341aaf42b5b0
2018-05-15 10:18:03 -07:00
..
filter
BUILD
capability.go
config.go Refactor the Sandbox package into Sandbox + Container. 2018-05-15 10:18:03 -07:00
controller.go Return better errors from Docker when runsc fails to start. 2018-05-09 14:13:37 -07:00
events.go
fds.go
fs.go Skip atime and mtime update when file is backed by host FD 2018-05-10 14:59:40 -07:00
limits.go
loader.go Return better errors from Docker when runsc fails to start. 2018-05-09 14:13:37 -07:00
loader_test.go Return better errors from Docker when runsc fails to start. 2018-05-09 14:13:37 -07:00
network.go
strace.go