mirror of
https://github.com/docker/docs.git
synced 2026-04-02 01:08:53 +07:00
a4f5e30249
* Reword lots of instances of 'will' * Reword lots of instances of won't * Reword lots of instances of we'll * Eradicate you'll * Eradicate 'be able to' type of phrases * Eradicate 'unable to' type of phrases * Eradicate 'has / have to' type of phrases * Eradicate 'note that' type of phrases * Eradicate 'in order to' type of phrases * Redirect to official Chef and Puppet docs * Eradicate gratuitous 'please' * Reduce use of e.g. * Reduce use of i.e. * Reduce use of N.B. * Get rid of 'sexagesimal' and correct some errors
76 lines
2.2 KiB
Markdown
76 lines
2.2 KiB
Markdown
---
|
|
description: Learn how to deploy containerized applications on a cluster, with Docker Universal Control Plane.
|
|
keywords: deploy, application
|
|
redirect_from:
|
|
- /ucp/deploy-application/
|
|
- /ucp/applications/deploy-app-cli/
|
|
title: Deploy an app from the CLI
|
|
---
|
|
|
|
With Docker Universal Control Plane you can deploy your apps from the CLI,
|
|
using Docker Compose. In this example we're going to deploy a WordPress
|
|
application.
|
|
|
|
## Get a client certificate bundle
|
|
|
|
Docker UCP secures your cluster with role-based access control, so that only
|
|
authorized users can deploy applications to the cluster. To run
|
|
Docker commands on the UCP cluster, you need to authenticate your requests using
|
|
client certificates.
|
|
|
|
[Learn how to set your CLI to use client certificates](../access-ucp/cli-based-access.md).
|
|
|
|
## Deploy WordPress
|
|
|
|
The WordPress application we're going to deploy is composed of two services:
|
|
|
|
* wordpress: The container that runs Apache, PHP, and WordPress.
|
|
* db: A MariaDB database used for data persistence.
|
|
|
|
<!-- would be better if this was a docker-compose v2 file-->
|
|
|
|
After setting up your terminal to authenticate using client certificates,
|
|
create a file named `docker-compose.yml` with the following service definition:
|
|
|
|
```yml
|
|
wordpress:
|
|
image: wordpress
|
|
links:
|
|
- db:mysql
|
|
ports:
|
|
- 8080:80
|
|
|
|
db:
|
|
image: mariadb
|
|
environment:
|
|
MYSQL_ROOT_PASSWORD: example
|
|
```
|
|
|
|
In your command line, navigate to the place where you've created the
|
|
`docker-compose.yml` file and run:
|
|
|
|
```bash
|
|
$ docker-compose --project-name wordpress up -d
|
|
```
|
|
|
|
Test that the WordPress service is up and running, and find where you can
|
|
reach it.
|
|
|
|
```bash
|
|
$ docker-compose --project-name wordpress ps
|
|
|
|
Name Command State Ports
|
|
------------------------------------------------------------------------------------------
|
|
wordpress_db_1 docker-entrypoint.sh mysqld Up 3306/tcp
|
|
wordpress_wordpress_1 /entrypoint.sh apache2-for ... Up 192.168.99.106:8080->80/tcp
|
|
```
|
|
|
|
In this example, WordPress can be accessed at 192.168.99.106:8080. Navigate to
|
|
this address in your browser, to start using the WordPress app you just
|
|
deployed.
|
|
|
|
|
|
|
|
## Where to go next
|
|
|
|
* [Deploy an app from the UI](deploy-app-ui.md) |