title: Docker Swarm Service - force update of latest image already running
body: <p>environment</p>
  
  <ul>
  <li>docker 1.12 </li>
  <li>clusted on Ubuntu 16.04</li>
  </ul>
  
  <p>Is there a way to force a rolling update to a docker swarm service already running if the service update is not changing any parameters but the docker hub image has been updated?</p>
  
  <p>Example: I deployed service: </p>
  
  <pre><code>docker service create --replicas 1 --name servicename --publish 80:80 username/imagename:latest
  </code></pre>
  
  <p>My build process has updated the latest image on docker hub now I want to pull the latest again.</p>
  
  <p>I have tried running:</p>
  
  <pre><code>docker service update --image username/imagename:latest servicename
  </code></pre>
  
  <p>When I follow this process, docker does not pull the latest, I guess it assumes that since I wanted latest and docker already pulled an image:latest then there is nothing to do.</p>
  
  <p>The only work around I have is to remove the service servicename and redeploy.</p>