-
**Description**
Swarm service / overlay breakage - starting container failed: Address already in use
Also reported by @nickjj who said it prevented a production roll-out of Swarm.
Possibl…
-
**Description**
I am having issues resolving DNS externally within my Docker Swarm environment. I'm making a simple request to an AWS SQS queue to pick up a message and process it. The requests…
-
## Expected behavior
That the status is the same for both sites.
## Actual behavior
This is what I get when I query the status for the site from which I initiated the site replication:
```
./mc…
-
## What did you do
Following the docs,
k3d registry create...
k3d cluster create --registry-use ...
works well together. While trying to debug a connectivity issue, I added --network ho…
-
Therefore, this test-case is currently disabled.
The root reason of this issue is maybe the docker server version:
a) On Travis CI: 19.03.8
b) On Circle CI: 18.06
-
**Description**
I have a swarm running with two nodes, and both nodes were leader.
I know this isn't recommended in raft consensus algorithm,
so I demoted one of the leaders, and after that I resta…
-
**Description**
Service containers seem to get 2 IP addresses (let's say x.y.z.2 and x.y.z.3) -- one ends up being the DNS name, and the other is inserted in /etc/hosts. The problem this causes is …
-
Describe the bug
A clear and concise description of what the bug is.
If you set up docker in rootless mode, you can not run the test
Setup docker rootless based on
https://docs.docker.com/e…
-
### Expected behavior
When adding Amazon Policy "AmazonEC2ContainerRegistryReadOnly" to the created cloud formation from Docker for AWS this should allow docker find images without having to use `a…
-
I have two services running a single container each, _on different nodes_, using same "overlay" network. When I try to ping one container from inside the other via service name, it fails:
```
ping ak…