Nicolas De loof
Nicolas De loof
`secrets` abstraction should be preferred over bind mount as this clarify role of mounts in container. Also will allow to benefit native support for secrets if/once docker engine introduce support...
By allowing paths to be relative, Compose always made the assumption docker daemon is local. This obviously isn't always the case, still this is obvious in the compose model in...
time ;)
> I’m wondering whether we should support this in compose-go, or if it should be handled on the client side instead? I looked into adding this to docker/compose first, but...
> The newer container is removed, which shouldn't be the case, the older container should be removed. nope, there's no reason the older is removed as long as both match...
rolling upgrade means image has been updated, and as such container should be detected not to be up-to-date and will be re-created
As you're basically bypassing compose logic intentionally, don't be surprised the result is not consistent with your expectations. What you're looking for is for compose to have an _actual_ rolling...
let me double check.
you're right, I created https://github.com/docker/compose/pull/12272 to cover this scenario Please note replica number (in container names) will grow each and every-time you use this "rolling upgrade" hack
Compose polls engine API to check container reach "healthy" state. But if it detects a container crash, I would not expect it silently ignores and let container restart. IMHO the...