gvisor/runsc
Justine Olshan c05660373e Moved restore code out of create and made to be called after create.
Docker expects containers to be created before they are restored.
However, gVisor restoring requires specificactions regarding the kernel
and the file system. These actions were originally in booting the sandbox.

Now setting up the file system is deferred until a call to a call to
runsc start. In the restore case, the kernel is destroyed and a new kernel
is created in the same process, as we need the same process for Docker.

These changes required careful execution of concurrent processes which
required the use of a channel.

Full docker integration still needs the ability to restore into the same
container.

PiperOrigin-RevId: 205161441
Change-Id: Ie1d2304ead7e06855319d5dc310678f701bd099f
2018-07-18 16:58:30 -07:00
..
boot Moved restore code out of create and made to be called after create. 2018-07-18 16:58:30 -07:00
cmd Moved restore code out of create and made to be called after create. 2018-07-18 16:58:30 -07:00
container Moved restore code out of create and made to be called after create. 2018-07-18 16:58:30 -07:00
fsgofer Make fsgofer attach more strict 2018-06-04 18:04:54 -07:00
sandbox Moved restore code out of create and made to be called after create. 2018-07-18 16:58:30 -07:00
specutils Modified error message for clarity. 2018-07-10 14:58:12 -07:00
test Bump the timeout when waiting for python HTTP server. 2018-07-13 12:34:04 -07:00
tools/dockercfg Add tool to configure runtime settings in docker 2018-06-20 13:01:16 -07:00
BUILD Refactor container_test in preparation for sandbox_test 2018-06-04 11:26:30 -07:00
main.go Sets the restore environment for restoring a container. 2018-06-29 14:47:40 -07:00