<commit_before>## Atomic: /usr/bin/atomic

The [`atomic` command](https://github.com/projectatomic/atomic) (`/usr/bin/atomic`) defines the entrypoint for Project Atomic hosts. 

On an Atomic host, you have two main software delivery vehicles:

 * rpm-ostree for managing the deployment and updates of the host system.
 * Linux containers (currently Docker) to provide containers running services and applications. 

The goal of `atomic` is to provide a high-level, coherent entrypoint for the system and to fill in gaps in Linux container implementations.

### Note about Atomic

The `atomic` command is still a bit new and undergoing rapid development. It is currently in Fedora 22 alpha and will soon be included in the CentOS Atomic host builds.

## Using /usr/bin/atomic

### `atomic run`

Atomic allows an image provider to specify how a container image expects to be run.

Specifically this includes the privilege level required.

For example if you built an 'ntpd' container application, that required the
SYS_TIME capability, you could add meta data to your container image using the
command:

```
LABEL RUN /usr/bin/docker run -d --cap-add=SYS_TYPE ntpd
```

Now if you executed `atomic run ntpd`, it would read the `LABEL RUN` json metadata from the container image and execute this command.

### `atomic install`
<commit_msg>Catching up with master Merge branch 'master' of github.com:projectatomic/atomic-site<commit_after>## Atomic: /usr/bin/atomic

The [`atomic` command](https://github.com/projectatomic/atomic) (`/usr/bin/atomic`) defines the entrypoint for Project Atomic hosts. 

On an Atomic host, you have two main software delivery vehicles:

 * rpm-ostree for managing the deployment and updates of the host system.
 * Linux containers (currently Docker) to provide containers running services and applications. 

The goal of `atomic` is to provide a high-level, coherent entrypoint for the system and to fill in gaps in Linux container implementations.

### Note about Atomic

The `atomic` command is still a bit new and undergoing rapid development. It is currently in the Fedora and CentOS Atomic host builds.

## Using /usr/bin/atomic

### `atomic run`

Atomic allows an image provider to specify how a container image expects to be run.

Specifically this includes the privilege level required.

For example if you built an 'ntpd' container application, that required the
SYS_TIME capability, you could add meta data to your container image using the
command:

```
LABEL RUN /usr/bin/docker run -d --cap-add=SYS_TYPE ntpd
```

Now if you executed `atomic run ntpd`, it would read the `LABEL RUN` json metadata from the container image and execute this command.

### `atomic install`

{'fraction_non_alphanumeric': 0.07011070110701106, 'fraction_numerical': 0.0007380073800738007, 'mean_word_length': 4.476767676767677, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, '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': '5499563', 'n_tokens_mistral': 721, 'n_tokens_neox': 678, 'n_words': 375}