@jayooin that's weird, if you use --with-registry-auth, you don't normally have to set up the credentials on each worker node as the credentials are passed to the wokers by the manager.
In my case the issue was that I was using a self-signed certificate for accessing the private docker registry. I had configured it correctly on the master node, but not on ...
In the placement section of the compose file, you can specify constraints. I'd recommend using node labels so you can add more potential nodes (should an existing node fail) without redefining any deployments bound to a node, but you can also specify hostnames. The result looks like:
Yes, you can and you should take advantage of the docker-compose app, see CI and CD are two different things, as you have running stack, so you have one basic version of application and its stack, Now needs to update those whenever you push changes to your app.
We have to push changes to application and build new image, once we have build and push the image ...