Is it safe to yum update docker-ce with containers running in swarm cluster?
I have three Scientific Linux (for this purpose, essentially CentOS) 7 machines configured as a Docker swarm. There is a pending update from docker-ce 18.06 to 18.09. Is it safer to do a process like this on each node in turn:
- set node to "drain"
- reassign leadership of the swarm if this node had it
- do the update of the node
- set the node back to "active"
Or is the RPM update process and the swarm management sufficiently smart that I can just "yum update" each node without worrying about the other steps?
docker centos7 docker-ce
add a comment |
I have three Scientific Linux (for this purpose, essentially CentOS) 7 machines configured as a Docker swarm. There is a pending update from docker-ce 18.06 to 18.09. Is it safer to do a process like this on each node in turn:
- set node to "drain"
- reassign leadership of the swarm if this node had it
- do the update of the node
- set the node back to "active"
Or is the RPM update process and the swarm management sufficiently smart that I can just "yum update" each node without worrying about the other steps?
docker centos7 docker-ce
add a comment |
I have three Scientific Linux (for this purpose, essentially CentOS) 7 machines configured as a Docker swarm. There is a pending update from docker-ce 18.06 to 18.09. Is it safer to do a process like this on each node in turn:
- set node to "drain"
- reassign leadership of the swarm if this node had it
- do the update of the node
- set the node back to "active"
Or is the RPM update process and the swarm management sufficiently smart that I can just "yum update" each node without worrying about the other steps?
docker centos7 docker-ce
I have three Scientific Linux (for this purpose, essentially CentOS) 7 machines configured as a Docker swarm. There is a pending update from docker-ce 18.06 to 18.09. Is it safer to do a process like this on each node in turn:
- set node to "drain"
- reassign leadership of the swarm if this node had it
- do the update of the node
- set the node back to "active"
Or is the RPM update process and the swarm management sufficiently smart that I can just "yum update" each node without worrying about the other steps?
docker centos7 docker-ce
docker centos7 docker-ce
asked Nov 15 '18 at 13:17
borisboris
11114
11114
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320365%2fis-it-safe-to-yum-update-docker-ce-with-containers-running-in-swarm-cluster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320365%2fis-it-safe-to-yum-update-docker-ce-with-containers-running-in-swarm-cluster%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown