<commit_before>[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-16-04-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-16-04-master/)
[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-17-04-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-17-04-master/)
[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-fedora-26-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-fedora-26-master/)
[![Go Report Card](https://goreportcard.com/badge/github.com/clearcontainers/proxy)](https://goreportcard.com/report/github.com/clearcontainers/proxy)
[![Coverage Status](https://coveralls.io/repos/github/clearcontainers/proxy/badge.svg?branch=master)](https://coveralls.io/github/clearcontainers/proxy?branch=master)
[![GoDoc](https://godoc.org/github.com/clearcontainers/proxy?status.svg)](https://godoc.org/github.com/clearcontainers/proxy/api)


# `cc-proxy`

`cc-proxy` works alongside the [Clear Containers runtime](
https://github.com/clearcontainers/runtime) and [shim](
https://github.com/clearcontainers/shim) to provide a VM-based [OCI runtime](
https://www.opencontainers.org/) solution.

`cc-proxy` is a daemon offering access to the [`agent`](
https://github.com/clearcontainers/agent) to both the runtime and shim
processes. Only a single instance of `cc-proxy` per host is necessary as it can
be used for several different VMs.
<commit_msg>doc: State one proxy per VM is now used<commit_after>[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-16-04-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-16-04-master/)
[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-17-04-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-azure-ubuntu-17-04-master/)
[![Build Status](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-fedora-26-master/badge/icon)](http://cc-jenkins-ci.westus2.cloudapp.azure.com/job/clear-containers-proxy-fedora-26-master/)
[![Go Report Card](https://goreportcard.com/badge/github.com/clearcontainers/proxy)](https://goreportcard.com/report/github.com/clearcontainers/proxy)
[![Coverage Status](https://coveralls.io/repos/github/clearcontainers/proxy/badge.svg?branch=master)](https://coveralls.io/github/clearcontainers/proxy?branch=master)
[![GoDoc](https://godoc.org/github.com/clearcontainers/proxy?status.svg)](https://godoc.org/github.com/clearcontainers/proxy/api)


# `cc-proxy`

`cc-proxy` works alongside the [Clear Containers runtime](
https://github.com/clearcontainers/runtime) and [shim](
https://github.com/clearcontainers/shim) to provide a VM-based [OCI runtime](
https://www.opencontainers.org/) solution.

`cc-proxy` is a daemon offering access to the [`agent`](
https://github.com/clearcontainers/agent) to both the runtime and shim
processes. Only a single instance of `cc-proxy` per host is necessary as it can
be used for several different VMs. Since [Clear Containers 3.0.10](https://github.com/clearcontainers/runtime/releases/tag/3.0.10),
one proxy instance per virtual machine is launched for improved isolation.

{'fraction_non_alphanumeric': 0.169327251995439, 'fraction_numerical': 0.01710376282782212, 'mean_word_length': 5.414990859232176, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 21, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3121190', 'n_tokens_mistral': 1247, 'n_tokens_neox': 1185, 'n_words': 159}