Limitations

Contents

1 Limitations

1 `Limitations`

This is still early code and the OCI standard has not yet reached version 1.0.0, hence there are a few feature gaps, cc-oci-runtime currently works with all the 1.0.0 release candidates.

The page documents those gaps, all of which are being worked on.

1.1 Networking

Basic Networking within the Clear Container is available:

1.1.1 Run a Clear Container using the default docker bridge network

$ sudo docker run -it --net=bridge $image

Or simply:

$ sudo docker run -it $image

1.1.2 Run a Clear Container with networking disabled (only localhost is available)

$ sudo docker run -it --net=none $image

1.1.3 Unsupported network types

--net=host: Doesn't make immediate sense when using a VM. It may be possible to "fake it" well enough for some use cases in the future (#81).
--net=containers: We don't support "joining" an already existing VM at the moment (#82)

1.1.4 Adding networks dynamically

The current OCI runtime doesn't support adding networks to an already running container using docker network connect. We currently only setup the VM network configuration with what is defined by the CNM plugin at startup time. It would be possible to watch the networking namespace to discover and propagate new networks at runtime but it's not implemented today (tracked in issue #388).

1.2 Annotations

OCI Annotations are not currently exposed inside the Clear Container.

See https://github.com/01org/cc-oci-runtime/issues/21

1.3 No checkpoint and restore commands

Although the runtime provides stub implementations of these commands, this is currently purely to satisfy Docker - the commands do NOT save/restore the state of the Clear Container.