[AURORA-1056] always send force_pull_image in ContainerInfo

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 0.8.0
• Assignee: Unassigned
• Reporter: Jay Buffington
• Created: 24/Jan/15 01:30
• Updated: 07/May/15 17:51
• Resolved: 26/Jan/15 16:27

Description

mesos 0.21 introduced "force_pull_image" which IMHO, is a terrible idea and changed existing behavior.

In 0.20 the image you specify will always be "docker pull"ed which means that if there was a newer version in the registry than the one in the cache you would get it.

After 0.21 force_pull_image defaults to false, so unless you make a code change the "docker pull" doesn't happen. This means that if your cache has an older copy of the image, you run whatever happens to be in the cache.

This results in starting 5 instances of the job, and 3 might one the old version (because it was cached on that slave) and 2 might one the new version (because those two slaves didn't have it cached), which is never what users want.

Issue Links

• relates to: AURORA-1014 Client binding_helper to resolve docker label to a stable ID at create