Limitations: docker compose: note it has issues

Note that docker compose has similar issues to docker swarm
when under Kata.

Fixes: #530

Signed-off-by: Graham Whaley <graham.whaley@intel.com>
This commit is contained in:
Graham Whaley 2019-08-13 17:51:11 +01:00
parent f8873a088f
commit f1b9c23040

View File

@ -8,7 +8,7 @@
* [events command](#events-command)
* [update command](#update-command)
* [Networking](#networking)
* [Docker swarm support](#docker-swarm-support)
* [Docker swarm and compose support](#docker-swarm-and-compose-support)
* [Resource management](#resource-management)
* [docker run and shared memory](#docker-run-and-shared-memory)
* [docker run and sysctl](#docker-run-and-sysctl)
@ -114,7 +114,7 @@ All other configurations are supported and are working properly.
## Networking
### Docker swarm support
### Docker swarm and compose support
The newest version of Docker supported is specified by the
`externals.docker.version` variable in the
@ -127,6 +127,8 @@ by the `externals.docker.meta.swarm-version` variable in the
See issue https://github.com/kata-containers/runtime/issues/175 for more information.
Docker compose normally uses custom networks, so also has the same limitations.
## Resource management
Due to the way VMs differ in their CPU and memory allocation, and sharing