Bash file completion not working for docker stack deploy -c

[geki007]

Description

I think since "new bash completion" the completion for docker stack deploy (-c arg) does not work like before

Reproduce

1. Open Terminal
2. Enable bash completion
3. docker stack deploy -c <PRESS TAB for bash file completion>

Expected behavior

-c ... does not complete filenames but it should
If you enter something or delete -c and press TAB you see it only completes stack names

docker version

Client: Docker Engine - Community
 Version: 29.1.2
 API version: 1.52
 Go version: go1.25.5
 Git commit: 890dcca
 Built: Tue Dec 2 21:55:45 2025
 OS/Arch: linux/amd64
 Context: default

Server: Docker Engine - Community
 Engine:
 Version: 29.1.2
 API version: 1.52 (minimum version 1.44)
 Go version: go1.25.5
 Git commit: de45c2a
 Built: Tue Dec 2 21:55:45 2025
 OS/Arch: linux/amd64
 Experimental: true
 containerd:
 Version: v2.2.0
 GitCommit: 1c4457e00facac03ce1d75f7b6777a7a851e5c41
 runc:
 Version: 1.3.4
 GitCommit: v1.3.4-0-gd6d73eb8
 docker-init:
 Version: 0.19.0
 GitCommit: de40ad0

docker info

Client: Docker Engine - Community
 Version: 29.1.2
 Context: default
 Debug Mode: false

Server:
 Containers: 6
 Running: 5
 Paused: 0
 Stopped: 1
 Images: 19
 Server Version: 29.1.2
 Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Using metacopy: false
 Native Overlay Diff: true
 userxattr: false
 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

Additional Info

cobra.ShellCompDirectiveNoFileComp could be the cause

cli/cli/command/stack/deploy.go

Line 48 in 890dcca

ValidArgsFunction: completeNames(dockerCLI),

cli/cli/command/stack/cmd.go

Line 64 in 890dcca

return names, cobra.ShellCompDirectiveNoFileComp

[thaJeztah]

Thanks for reporting; you're on the right path, but I don't think the lines you linked to are the ones responsible for this.

In this case, it's because we chose to disable completion for filenames / paths by default for flags; the default is to complete any flag with files, which in 99% of the case is incorrect, so we disabled that functionality;

• cli: disable file-completion by default #6447

For flags that SHOULD provide completion for filenames, we require a completion function to be defined for that flag; similar to

cli/cli/command/container/completion.go

Line 127 in 890dcca

_ = cmd.RegisterFlagCompletionFunc("env-file", completion.FileNames())

So, it looks like that just wasn't implemented yet, but should be easy to add.

[geki007]

For me it's a bug if it was working before :-)

Thanks for the fast and informative response. Now i'm just waiting for the enhancement

[thaJeztah]

I opened a PR to implement it; #6690

[geki007]

Wow and thanks!