Things to make Docker go on Ops Works. We need help.</pakled>
Described in this blog post of mine and based on this AWS blog entry
- Set up a new stack in OpsWorks. Under Advanced set the following:
- Chef version: 11.10
- Use custom Chef cookbooks: https git url to a repo containing the other files in the gist inside owdocker/recipes/
- 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 ala quay.io/yourusername/yourimage:$registry_tag
- 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
- registry_username: OPTIONAL username to login to the registry
- registry_password: OPTIONAL password to login to the registry
- registry_url: OPTIONAL url to a non hub.docker.com registry ala quay.io
Chris,
I get what the apt cookbook is doing now. ( Updating apt to the latest before it runs any apt-get commands)
I changed that to the yum-epel cookbook and will see what works from there.
It does in fact break down because of the metadata.rb file.
Thanks so much for your help!,
J