Redeploy of the stack is fine but it wouldn’t create any networks, secrets, configs, that are defined as external resources. My main question is where are these things stored if not under /var/lib/docker/swarm? Why is this different than the normal swarm config? And what is considered best practices to backup the cluster (docker swarm for aws)?
This is specifically for “docker swarm on aws” ONLY.
I was thinking maybe combine docker-compose to create the resources first including the secrets since they can reference local files before you deploy the stack.
Right now the way I have it is I have a shell script that initializes the base networks before I deploy the stacks. But after writing this I think I can probably make it more portable by using docker-compose.
However that still does not address your question on what do you need to backup.
Right… The main point is I should be able to backup the swarm as the documentation states. I’m not sure where else to look or who else to ask? Very frustrating
Did you check if the mount was overwritten? In my case I had a bind mount in a container but I set the propagation incorrectly and it “layered” a new mount hiding some of my other mounts.
I might be wrong, but when you ssh into an instance your actually running inside a container called shell. You’re not running a shell in the EC2 instance itself. Take a look at this article.