Services won't automatically re-deploy about shepherd HOT 7 CLOSED

As I found out, in my case shepherd failed updating a certain service because the mazzolino/shepherd:0.2 image was still on an older, incompatible docker base image. I recently rebuilt the 0.2 image. That fixed my problems.

from shepherd.

I think I am seeing this myself. Might have a closer look soon,

from shepherd.

@djmaze Hi ! Thank you for your work, I'm actually trying to use your tool on my docker swarm, and was not working.

I tried two tags for your image: 0.2 (blocked on docker service update for your image ) and latest. Latest doesn't block and actually does the update every 5 mins. But the running container is still not updated. I'm on the latest version of docker.

@gbhrdt where did you add these options ?

If anyone could make it work I'd really appreciate some help, thank you ! :)

EDIT: Ok I'm sorry, it works... I had to use the "with auth" option.. Guess I was too rushy !! :p

btw, in my opinion the redirection on /dev/null disable and / or verbosity if people wants it. Might be a good idea to let the user decide thanks to an option !

from shepherd.

Sorry for the late answer. I currently have no time to reproduce this. Maybe others can jump in?

from shepherd.

@djmaze Currently I am successfully re-deploying the services manually by providing --force and --image [IMAGE_TAG] to docker update. This works for me! Maybe we can just add those parameters.

from shepherd.

Ready to close this issue?

from shepherd.

Seems not to be a problem anymore.

from shepherd.