- Presented by Portworx
- Using Docker Birthday on Mac 1.12 beta
- Distributed Application Bundles (DAB)
bundle,deployandstack
- Birthday running on swarm in the Cloud
- Cloud - droplets built to 1.12 by hand
- DAB experimental
- no
deployorstack
- no
- Hand rolled script
- Show mesh routing (hitting app on both nodes)
- host names are important (i.e. unique)
- Appears that without exposed ports tasks/containers don't end up on default overlay network
- we created our own overlay network and added services to it directly
- scale redis
- App may/may not be resilient
- 12 Factor
- Rolling upgrade of redis
- set update-delay on service
- move to new version of the image
- Scale it back down
- Creating a service is easy
- Rolling upgrade built in - need to update the service to support it or create it with the setting initially
- Handles service failures, node failures seamlessly
- Services scale up and down with a simple command (change to replica count not +- number)
- Digital hosting is pretty slick
- Couldn't run birthday party example w/o several changes (volumes, networks, links)
- DigitalOcean default droplets 1.11 requiring installation by hand
- Stacks and DAB files are still experimental in 1.12. On Mac (probably Windows) experimental features are turned on. On ubuntu, you have to pull the source and rebuild docker with experimental features turned on. Expermental features
- Creating DAB file removes top level networks but not the networks defined for each service (container)
- If using links and the environment variables it creates, then your services won't be able to communicate - if you rely on the link variables and not name resolution. See 12 factor app paterns
- When creating a DAB, docker-compose file needs image attribute it can't just have build command
- Side note When pulling images from dockerhub we received a
403 repository lockedmessage. We changed the image to be private then back to public to fix it.