[
https://issues.apache.org/jira/browse/MESOS-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Buffington updated MESOS-2312:
----------------------------------
Description:
MESOS-1886 changed default behavior. Prior to commit 8682569d being merged,
docker pull was always executed before a "docker run". If I'm reading the
commit correctly, docker pull is now only executed when
DockerInfo.force_docker_pull is specified as true in the protobuf.
We can't change behavior like this without a deprecation cycle.
Make force_docker_pull to default to true before any releases with this change
go out, i.e. 0.22.0
was:
MESOS-1886 changed default behavior. Prior to commit 8682569d being merged,
docker pull was always executed before a "docker run". If I'm reading the
commit correctly, docker pull is now only executed when
DockerInfo.force_docker_pull is specified in the protobuf.
We can't change behavior like this without a deprecation cycle.
Make force_docker_pull to default to true before any releases with this change
go out, i.e. 0.22.0
> DockerInfo.force_pull_image should default to true to preserve existing
> behavior
> --------------------------------------------------------------------------------
>
> Key: MESOS-2312
> URL: https://issues.apache.org/jira/browse/MESOS-2312
> Project: Mesos
> Issue Type: Bug
> Components: docker
> Reporter: Jay Buffington
>
> MESOS-1886 changed default behavior. Prior to commit 8682569d being merged,
> docker pull was always executed before a "docker run". If I'm reading the
> commit correctly, docker pull is now only executed when
> DockerInfo.force_docker_pull is specified as true in the protobuf.
> We can't change behavior like this without a deprecation cycle.
> Make force_docker_pull to default to true before any releases with this
> change go out, i.e. 0.22.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
