Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Bad wording/missing information for live restore and swarm mode

Abierto Apto para principiantes
  • ¿Algo no está bien?
#26,424 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
82/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, markdown
Área
documentation

Línea de trabajo

Empieza por el párrafo sobre live restore y swarm de la página enlazada en el issue. Comprueba que la redacción coincida con el comportamiento del daemon informado: habilitar live restore en un miembro de swarm impide que el daemon se inicie. Reescribe el párrafo para indicar claramente qué configuraciones están permitidas y qué ocurre cuando se habilitan ambas opciones.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

status/triage
Is this a docs issue?
  • My issue is about the documentation content or website
Type of issue

Information is incorrect

Description

Hi there,
your original text for having live restore and swarm mode is incorrect or better said, inconsistent.

The way the paragraph is written suggests that in mixed-case scenario (which is perfectly legal), containers running as standalone will be managed with live restore, while containers running as services in swarm mode, would be managed by swarm.

Therefore, if one would enable live restore in daemon.js on a system that is both a swarm member and has standalone containers, one would expect both to work.

That is not true because docker implementation straight-up refuses to start the daemon if both live restore are enabled and node is part of a swarm:

Oct 23 12:28:39 msi dockerd[3191]: time="2026-10-23T12:28:39.195135279+02:00" level=info msg="Loading containers: done." Oct 23 12:28:39 msi dockerd[3191]: time="2026-10-23T12:28:39.218291222+02:00" level=info msg="Docker daemon" commit=0367cbe containerd-snapshotter=false storage-driver=overlay2 version=29.9.2 Oct 23 12:28:39 msi dockerd[3191]: time="2026-10-23T12:28:39.218905151+02:00" level=info msg="Daemon shutdown complete" error="failed to start cluster component: --live-restore daemon configuration is incompatible with swarm mode" Oct 23 12:28:39 msi dockerd[3191]: time="2026-10-23T12:28:39.218938380+02:00" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=moby Oct 23 12:28:39 msi dockerd[3191]: failed to start cluster component: --live-restore daemon configuration is incompatible with swarm mode Oct 23 12:28:39 msi dockerd[3191]: time="2026-10-23T12:28:39.218939560+02:00" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby Oct 23 12:28:39 msi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE

Location

https://docs.docker.com/engine/daemon/live-restore/

Suggestion

Please rewrite the live restore and swarm paragraph to explicitly say that trying to enable live restore on a node that is already a swarm member will break running docker daemon, and that it has to be only one of them: live restore is only for non-swarm node (no mixed mode possible) or if node is swarm member, live restore is not possible.
Or something similar but very precise what is allowed and what will break your system.

Of course, the best solution would be to have both options working for mixed mode cases, where docker would simply ignore swarm orchestrated containers on a swarm node and just manage standalone containers when live restore is enabled.

Lenguaje dominante
Markdown
Estrellas
4.7k
Forks
8.5k
Merge medio
1 d 22 h
PR fusionados (30 d)
133

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de docker/docs

Todos los issues de docker/docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.