-
Notifications
You must be signed in to change notification settings - Fork 92
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
169 changed files
with
1,765 additions
and
7,809 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,6 +3,7 @@ package.list | |
|
|
||
| # robot | ||
| robot-logs/ | ||
| pabot_results/ | ||
| log.html | ||
| report.html | ||
| output.xml | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| # Download PDF Documentation # | ||
|
|
||
| - <a href="./pdf/vic_12_overview.pdf" target="_blank">Overview of vSphere Integrated Containers</a> | ||
| - <a href="./pdf/vic_12_vsphere_admin.pdf" target="_blank">Install, Deploy, and Maintain the vSphere Integrated Containers Infrastructure</a> | ||
| - <a href="./pdf/vic_12_cloud_admin.pdf" target="_blank">Configure and Manage vSphere Integrated Containers</a> | ||
| - <a href="./pdf/vic_12_app_dev.pdf" target="_blank">Develop Container Applications with vSphere Integrated Containers</a> | ||
| - <a href="./pdf/vic_13_overview.pdf" target="_blank">Overview of vSphere Integrated Containers</a> | ||
| - <a href="./pdf/vic_13_vsphere_admin.pdf" target="_blank">Install, Deploy, and Maintain the vSphere Integrated Containers Infrastructure</a> | ||
| - <a href="./pdf/vic_13_cloud_admin.pdf" target="_blank">Configure and Manage vSphere Integrated Containers</a> | ||
| - <a href="./pdf/vic_13_app_dev.pdf" target="_blank">Develop Container Applications with vSphere Integrated Containers</a> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,7 +2,7 @@ | |
|
|
||
| Having examined some of the considerations around deploying single containers to a Virtual Container Host (VCH), this section examples how to deploy applications that are comprised of multiple containers. | ||
|
|
||
| There are two approaches you can take to this. The most instictive approach would be to create scripts that manage the lifecycle of volumes, networks and containers. | ||
| There are two approaches you can take to this. The most instinctive approach would be to create scripts that manage the lifecycle of volumes, networks and containers. | ||
|
|
||
| The second approach is to use a manifest-based orchestrator such as Docker Compose. VIC 1.1 has some basic support for Docker Compose, but it is not functionally complete. Docker Compose is a proprietary orchestrator that drives the Docker API and ties other pieces of the Docker ecosystem together including Build and Swarm. Given that VIC engine doesn't currently support either Build or Swarm, Compose compatibility is necessarily limited. However, Compose can still be a useful tool, provided those limitations are understood. | ||
|
|
||
|
|
@@ -48,7 +48,7 @@ docker network create --internal db-net | |
| docker network create web-net | ||
| # start the database container - specify a subdirectory on the volume as the data dir | ||
| docker run -d --name $DB_CTR_NAME --net db-net -v db-data:/var/lib/mysql --cpus 1 -m 2g -e MYSQL_ROOT_PASSWORD=somewordpress -e MYSQL_DATABASE=$DB_PASSWORD -e MYSQL_USER=$DB_USER -e MYSQL_PASSWORD=wordpress mysql:5.7 --datadir=/var/lib/mysql/data | ||
| docker run -d --name $DB_CTR_NAME --net db-net -v db-data:/var/lib/mysql --cpus 1 -m 2g -e MYSQL_ROOT_PASSWORD=somewordpress -e MYSQL_DATABASE=$DB_PASSWORD -e MYSQL_USER=$DB_USER -e MYSQL_PASSWORD=wordpress mysql:5.7 | ||
| # start the web container - note it resolves the database container by name over db-net | ||
| docker create --name $WEB_CTR_NAME --net web-net -p 8080:80 -v html-data:/var/www/html --cpus 2 -m 4g -e WORDPRESS_DB_HOST=$DB_CTR_NAME:3306 -e WORDPRESS_DB_USER=$DB_USER -e WORDPRESS_DB_PASSWORD=$DB_PASSWORD wordpress | ||
|
|
@@ -200,7 +200,7 @@ docker-compose down --volumes --rmi # stop the application and remove all res | |
|
|
||
| Given that VIC engine does not have a native build capability, it does not interpret the `build` keyword in a compose file and `docker-compose build` will not work when `DOCKER_HOST` points to a VIC endpoint. VIC engine relies upon the portability of the docker image format and it is expected that a regular docker engine will be used in a CI pipeline to build container images for test and deployment. | ||
|
|
||
| There are two ways to work around this. You can create separate Compose files for build and run, or you can use the same Compose file but just make sure to add a couple of arguments. We will explore both options here using another example of a Compose file that includes build instructions. In this case, the sample voting application found [here](https://github.com/dockersamples/example-voting-app/blob/master/docker-compose-simple.yml) | ||
| There are two ways to work around this. You can create separate Compose files for build and run, or you can use the same Compose file but just make sure to add a couple of arguments. We will explore both options here using another example of a Compose file that includes build instructions. In this case, the sample voting application found [here](https://github.com/dockersamples/example-voting-app/blob/master/docker-compose-simple.yml). | ||
|
|
||
| Let's start by cloning the repository: `git clone [email protected]:dockersamples/example-voting-app.git` and we'll start by looking at `docker-compose-simple.yml`. | ||
|
|
||
|
|
@@ -253,8 +253,6 @@ services: | |
| db: | ||
| image: postgres:9.4 | ||
| environment: | ||
| PGDATA: /var/lib/postgresql/data/data # Added as a workaround to /lost+found in volume root | ||
| result: | ||
| image: <registry-address>/<project>/result:0.1 # Fully-qualified image name | ||
|
|
@@ -276,10 +274,6 @@ Local volume mounts are useful for development and testing as they allow source | |
|
|
||
| VIC engine cannot map volumes from a local filesystem into a container because VIC engine containers are strongly isolated and don't share a common filesystem. Despite this, it is still possible in VIC to add state to a container by pre-populating a volume with data and mounting it (TBD: link to "Pre-populate a Volume"). | ||
|
|
||
| - Workaround to `/lost+found` folder | ||
|
|
||
| In VIC a Volume is an ext4 formatted disk. As such, it has `/lost+found` in the root. Some containers will not write data into this directory due to the presence of this folder, so in this case of postgres above, it is configured to create and write to a subdirectory of the mount point. | ||
|
|
||
| ***Combining into a single Compose file*** | ||
|
|
||
| If separate Compose files feels clunky, it's quite possible to build, push and run from the same Compose file. All we need to do is to merge them together and then make sure we tell docker-compose what we want. Here's an example of a merged file: | ||
|
|
@@ -305,8 +299,6 @@ services: | |
| db: | ||
| image: postgres:9.4 | ||
| environment: | ||
| PGDATA: /var/lib/postgresql/data/data | ||
| result: | ||
| build: ./result | ||
|
|
@@ -337,7 +329,6 @@ This is partly a question of functional completeness of VIC engine docker API su | |
|
|
||
| - VIC engine supports version 2 of the Compose File format. | ||
| - VIC engine has no native build support. | ||
| - VIC volumes are disks and when mounted, have a `/lost+found` folder created by ext4. For some containers - databases in particular - you will need to configure them to use a subdirectory of the volume. See MySQL example above. | ||
| - VIC containers take time to boot and thus may exhibit timing related issues. Eg. You may need to set `COMPOSE_HTTP_TIMEOUT` to a higher value than the default. | ||
| - VIC containers have no notion of local read-write shared storage. | ||
|
|
||
|
|
||
Oops, something went wrong.