dobi icon indicating copy to clipboard operation
dobi copied to clipboard

Add a stack resource

Open dnephin opened this issue 8 years ago • 8 comments

A stack resource would create/remove a Docker Stack.


stack=devenv:
  name: dev
  files: [...]
  prune: true|false
  with-registry-auth: true|false

At the same time we should deprecate the compose resource, since it can be replaced by a stack resource.

dnephin avatar Jun 04 '17 17:06 dnephin

right now at the place I work we use a docker-compose to deploy a docker stack. Should the dobi Stack resource deprecate the compose file itself? Or would just call the stack files?

cescoferraro avatar Nov 07 '17 22:11 cescoferraro

I think it would use github.com/docker/cli/cli/compose as a library, so would only support Compose v3.x.

I guess it would deprecate the compose resource, but not the compose file. A stack resource would still read compose files.

dnephin avatar Nov 07 '17 22:11 dnephin

I would be awesome if dobi could somehow repull all images when you do a "redeploy" by calling deploy on a already deployed stack. To avoid this https://github.com/moby/moby/issues/30951

cescoferraro avatar Nov 07 '17 22:11 cescoferraro

I think that is fixed in 17.09: https://github.com/moby/moby/issues/30951#issuecomment-342647614

dnephin avatar Nov 07 '17 22:11 dnephin

@dnephin if I update docker locally, would docker-machine create a machine running my updated version?

cescoferraro avatar Nov 10 '17 18:11 cescoferraro

docker-machine always uses an iso I think, so I don't think so. Is that related?

dnephin avatar Nov 10 '17 19:11 dnephin

The --resolve-image fix is great for us. I was wondering how to deploy it without waiting for docker-machine to bump version.

cescoferraro avatar Nov 10 '17 19:11 cescoferraro

Ah, I see! docker-machine should have that version already, I'm not sure why it wouldn't

dnephin avatar Nov 10 '17 19:11 dnephin