You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
We need to update the versions database to clarify that somehow. I vote for adding a reference to the issue in question using a new swarm-issue value like this:
docker:
description: "Moby project container manager"
notes: "Docker Swarm requires an older version of Docker."
url: "https://github.com/moby/moby"
version: "v17.12-ce"
meta:
swarm-version: "1.12.1"
swarm-issue: "https://github.com/kata-containers/runtime/issues/175"
The text was updated successfully, but these errors were encountered:
@jodh-intel, I have a question regarding this issue, it is possible to launch Swarm replicas with Docker 17.12.1, however, it is not possible to ping among the replicas mainly because of issue #175. The tests that were added check basics like interface names (#175). By using the version 1.12.1 is possible to ping among the replicas and do more complex stuff. Should I change the versions.yaml with docker 17.12.1? Thanks for everything.
zklei
pushed a commit
to zklei/runtime
that referenced
this issue
Jun 13, 2019
With this patch the runtime will communicate to the agent the
number of vCPUs that were hot added, allowing to the agent online all vCPUs.
The agent will try to online all vCPUs 10 times, waiting 100 milliseconds
in each iteration, this is needed since when the runtime calls to QMP
`device_add`, QEMU doesn't allocate all vCPUs inmediatelly.
fixeskata-containers#181
Signed-off-by: Julio Montes <[email protected]>
We currently document that docker 1.12 is required for using swarm in the versions database:
However, that's not strictly true since "basic" swarm works:
We need to update the versions database to clarify that somehow. I vote for adding a reference to the issue in question using a new
swarm-issue
value like this:The text was updated successfully, but these errors were encountered: