-
**Description**
**Steps to reproduce the issue:**
1. Created a swarm with 3 nodes some month ago
2. Run `docker node update --availability drain node01`
3. Shutdown node and reinstall wi…
-
#### Overview of the Issue
I'm trying to federate two consul clusters, a primary one with three server nodes and a secondary one with three server nodes.
When starting the replication, i get a…
-
Just bringing it up now because the call for papers came out recently, so before I forget. I am planning to go but it's in Boston, so @lbestock you might be able to go as well (since I don't think it …
-
I don't understand why we force the use of the `nats-io` namespace here.
It's a huge limitation only to foolproof people trying to deploy many nats-operators in different namespaces !
At least, ad…
-
**Description**
I have a docker swarm consisting of 3 docker master nodes, and no docker workers. The docker nodes are hosting multiple services, most of which are using the default overlay network, …
ghost updated
2 years ago
-
**Description**
Recently had an issue with D4AWS and lost quorum with my 3 managers. The Lead manager was still present and I was able to recover the swarm using `docker swarm init --force-new…
-
This is the top priority for supporting Cloud. Also seeking convergence with Docker4X (Editions). The requirements are
- Ensure a Swarm-compatible networking environment exists
- On IaaS provider…
-
**Description**
I am creating a stack with a custom network that I named `[stackname]_ingress` as follows:
```
version: '3.3'
networks:
ingress:
driver: overlay
ipam:
driver: d…
-
In regular non-swarm mode I can start and use a container with a glusterfs volume using this plugin. However in swarm/service mode, the container always fails to start. Having created a volume called …
-
Hi, I'm not sure if flexible signature isn't supported in `dash-extension` for `ServersideOutput` or it's an error so I'll be stating my question anyway.
Example code:
```
from dash_extensions.…