Name: opsworks-docker
Owner: DaWanda Engineering Team
Description: Make Docker go on Ops Works
Created: 2015-03-25 14:37:07.0
Updated: 2015-03-25 14:37:07.0
Pushed: 2015-03-22 19:57:18.0
Homepage:
null
Size: 83
Language: Ruby
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Email | Most Recent Commit | # Commits |
|---|
README
opsworks-docker
Make Docker go on Ops Works</pakled>
Based on this AWS blog entry
Instructions
- Set up a new stack in Ops Works. Under Advanced set the following:
- Chef version: 11.10
- Use custom Chef cookbooks: https git url to this repo
- Manage Berkshelf: Yes
- Berkshelf version: 3.1.3
- Add a layer
- Type: Other
- Recipes
- Setup: owdocker::install
- Deploy: owdocker::docker-image-deploy
- Add an App
- Type: Other
- Repository type: Other
- Environment variables:
- registry_image: The path portion of a docker pull command ala: docker pull {{ registry image }}
- registry_tag: The tag of the image that should be pulled from the registry
- layer: The shortname of the layer the image should be deployed to
- service_port: The port on the HOST that will be connected to the container
- container_port: The port on the CONTAINER that will be connected to the service port
- volumes: OPTIONAL argument to be passed as -v options (e.g. “/src/webapp:/opt/webapp”)
- registry_url: OPTIONAL url to a non hub.docker ala quay.io
- registry_username: OPTIONAL username to login to the registry
- registry_password: OPTIONAL password to login to the registry
- registry_email: OPTIONAL email to login to the registry
