Switch to host networking for docker on master
Host networking is now available on Docker for newer versions. This depends on upgrading Docker, but simplifies many iptables requirements. It will also reduce dependency on dhcrelay.
Benefits (host networking and new docker):
* Remove need for iptables workarounds to clean up where docker 0.10 fails
* Remove need for umount workarounds when stopping containers
* Docker runs faster
* New version does not have ip provisioning duplicate bug
Cons:
* Requires rework of upgrade/rollback script
* Upgrade needs to stop all containers before upgrade
* Upgrade needs to back up old containers before host upgrade
* Rollback requires downgrade of docker and purge of 6.0 containers first (they won't be backward compatible to 0.10)
* Rollback should require backup of /var/lib/docker directory just in case. Backing up devicemapper block device needs a bit of research to improve performance. Alternatively, we could just save 5.x containers to disk with dockerctl backup.
Blueprint information
- Status:
- Started
- Approver:
- Vladimir Kuklin
- Priority:
- Medium
- Drafter:
- Matthew Mosesohn
- Direction:
- Approved
- Assignee:
- Matthew Mosesohn
- Definition:
- Approved
- Series goal:
- Accepted for 6.1.x
- Implementation:
- Needs Code Review
- Milestone target:
- 6.1
- Started by
- Matthew Mosesohn
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Run docker containers with host networking
Addressed by: https:/
Add root workdir for nginx contianer
Addressed by: https:/
Add nsenter container
Addressed by: https:/
Use --net=host for containers, remove cobbler hack
Addressed by: https:/
Create persistent directories for container data