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

[BUG] `mode` attribute in `configs` works but raises an unsupported warning

Abierto
  • ¿Algo no está bien?
#14,288 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@ndeloof ya está trabajando en esto.

Desde el 8/10/2026.

  • #14297 de @NisargJasani0602 — cerrado sin fusionar
  • #14299 de @ndeloof — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker-compose, go
Área
backend, devtools

Línea de trabajo

Start by reproducing the warning with the Compose file in the issue and inspect the code that validates or reports the mode attribute for configs; the issue does not name a source file or test. Compare the warning with the observed file permissions, then run the relevant Compose tests. Done means the warning accurately reflects the supported behavior while the requested mode continues to work.

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

Descripción

kind/bug
Description

The latest version of compose raises the following warning when the mode attribute is provided under configs, even though it works as expected:

WARN[0000] service "test": configs.start.sh.mode: mode is not supported outside Swarm mode and will be ignored
  • With mode:
test-1  | -rwx------    1 root     root            52 Oct  6 11:52 /start.sh
  • Without mode:
test-1  | -r--r--r--    1 root     root            52 Oct  6 11:54 /start.sh

PoC:

services:
  test:
    image: alpine
    command: sh /start.sh
    configs:
      - source: start.sh
        target: /start.sh
        mode: 0700

configs:
  start.sh:
    content: |
      #!/usr/bin/env sh
      ls -l /start.sh
      tail -f /dev/null
Steps To Reproduce
  1. Create a compose file with the configs section and mode
  2. Start the container: docker compose up
  3. Observe the file permissions and the logged warning
Compose Version
Docker Compose version v5.6.0
Docker Environment
Client: Docker Engine - Community
 Version:    29.8.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.37.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.6.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 13
  Running: 13
  Paused: 0
  Stopped: 0
 Images: 61
 Server Version: 29.8.2
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ee2735368117d2eb259779949d5e75cdafec9761
 runc version: v1.5.1-0-g8f2685a4
 init version: de40ad0
 Security Options:
  apparmor
   Profile: default
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 7.0.0-38-generic
 Operating System: Linux Mint 22.3
 OSType: linux
 Architecture: x86_64
 CPUs: 22
 Total Memory: 30.85GiB
 Name: xxx
 ID: xx-xxx-xxx-xxx-xxx
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Username: xxxx
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
  ::1/128
 Live Restore Enabled: false
 Default Address Pools:
   Base: 172.16.0.0/12, Size: 24
 Firewall Backend: iptables
  EnableUserlandProxy: true
  UserlandProxyPath: /usr/bin/docker-proxy
Anything else?

No response

Lenguaje dominante
Go
Estrellas
38.4k
Forks
5.9k
Merge medio
2 d 5 h
PR fusionados (30 d)
62

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/compose

Todos los issues de docker/compose

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.