Is there a way to turn off the following promotional message?
“What’s next?
Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug sqlserver
Learn more at docker debug | Docker Docs ”
It seems to be appended to the return message from running the following type of command:
docker exec -it sqlserver /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P “ZZZZZZ” -Q “SELECT Name from sys.Databases”
Name
--------------------------------------------------------------------------------------------------------------------------------
master
tempdb
model
msdb
AdventureWorksDW2022
(5 rows affected)
What's next?
Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug sqlserver
Learn more at https://docs.docker.com/go/debug-cli/
System: Win 11 + WSL2 + Docker Desktop
2 Likes
oojacoboo
(Jacob Thomason)
April 19, 2024, 5:13am
2
Also would like to know - annoying.
For those wanting a quick fix, you may be able to leave off the interactive (-i
) flag on your docker commands. For us a simple:
docker exec -t bin/run-tests
…is sufficient. If you need an interactive shell, we’ll have to wait for Docker to offer an option to remove this new spam idea someone cooked up.
1 Like
thetwam
(Thetwam)
April 22, 2024, 2:59pm
3
Looks like there’s an environment variable DOCKER_CLI_HINTS
. Setting that to false
removed the spam for me.
DOCKER_CLI_HINTS=false
2 Likes
I am trying to follow these instructions…
opened 05:19PM - 05 Aug 23 UTC
area/gui
status/triage
### Description
In _Settings > General_ there is a setting named _Show CLI hint… s_.
This option is supposed to enable/disable hints in the CLI such as this one:
```
What's Next?
View summary of image vulnerabilities and recommendations → docker scout quickview alpine
```
However, no matter if the option is checked/unchecked, the hints are always displayed in the CLI:
```
$ docker pull alpine
Using default tag: latest
latest: Pulling from library/alpine
31e352740f53: Pull complete
Digest: sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1
Status: Downloaded newer image for alpine:latest
docker.io/library/alpine:latest
What's Next?
View summary of image vulnerabilities and recommendations → docker scout quickview alpine
```
The only way to disable these hints is to manually set `DOCKER_CLI_HINTS=false` in the environment.
### Reproduce
1. Run `unset DOCKER_CLI_HINTS` to ensure the CLI uses this setting from the UI.
2. Run `docker pull alpine`
3. Observe the following CLI hint displayed in the console:
```
What's Next?
View summary of image vulnerabilities and recommendations → docker scout quickview alpine
```
4. In the Docker UI, under _Settings > General_, uncheck the _Show CLI hints_ option and restart Docker (*).
5. Run `docker pull alpine` again and observe the CLI hint above still being shown.
(*): I'm not sure if a restart is truly necessary but I did anyway to make sure.
### Expected behavior
I expect the CLI tools to respect/use the _Show CLI hints_ option in the UI when `DOCKER_CLI_HINTS` is not set.
When the option is checked, I expect the following output:
```
$ docker pull alpine
Using default tag: latest
latest: Pulling from library/alpine
31e352740f53: Pull complete
Digest: sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1
Status: Downloaded newer image for alpine:latest
docker.io/library/alpine:latest
What's Next?
View summary of image vulnerabilities and recommendations → docker scout quickview alpine
```
When the option is unchecked, I expect the following output:
```
$ docker pull alpine
Using default tag: latest
latest: Pulling from library/alpine
Digest: sha256:82d1e9d7ed48a7523bdebc18cf6290bdb97b82302a8a9c27d4fe885949ea94d1
Status: Image is up to date for alpine:latest
docker.io/library/alpine:latest
```
### docker version
```bash
Client: Docker Engine - Community
Cloud integration: v1.0.35-desktop+001
Version: 24.0.5
API version: 1.43
Go version: go1.20.6
Git commit: ced0996
Built: Fri Jul 21 20:35:45 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Desktop
Engine:
Version: 24.0.5
API version: 1.43 (minimum version 1.12)
Go version: go1.20.6
Git commit: a61e2b4
Built: Fri Jul 21 20:35:45 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.21
GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc:
Version: 1.1.7
GitCommit: v1.1.7-0-g860f061
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```
### docker info
```bash
Client: Docker Engine - Community
Version: 24.0.5
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.1
Path: /usr/local/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.20.2-desktop.1
Path: /usr/local/lib/docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /usr/local/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /usr/local/lib/docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.6
Path: /usr/local/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/local/lib/docker/cli-plugins/docker-sbom
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /usr/local/lib/docker/cli-plugins/docker-scan
scout: Command line tool for Docker Scout (Docker Inc.)
Version: 0.20.0
Path: /usr/local/lib/docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 24.0.5
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: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
NodeID: k0zfz02a1y8gx1ghh8f7thkmk
Is Manager: true
ClusterID: q3xywnn0uzlwswsvhuib2mg1c
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
Data Path Port: 4789
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 192.168.65.4
Manager Addresses:
192.168.65.4:2377
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version: v1.1.7-0-g860f061
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.90.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.829GiB
Name: docker-desktop
ID: fcf0b2e6-9f44-4d46-8267-00745d6367a4
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
```
### Diagnostics ID
88FDDC42-D772-4400-813F-EA0779F83ABC/20230805171642
### Additional Info
_No response_
When I go to Docker Desktop > Settings > Show CLI hints > Uncheck > Apply & restart…
The spam is no longer returns from docker commands (linux terminal).
The spam still returns for docker commands prefixed with sudo (linux terminal).
1 Like
serafim
(Alex Kiselyov)
May 10, 2024, 9:17am
6
Is any solution for this. because untick setting didn’t work for me.
Getting useless hints after each second row in terminal already pisses me off.
The DOCKER_CLI_HINTS environment variable worked for me. In case others encounter the same situation, I use Docksal (similar to Lando, DDev, etc.) that spins up Docker containers configured for my project. Those containers, all need the variable present. With some of these applications, simply establishing the variable on your host machine is not sufficient. So, if you use similar setups for app development you’ll need to figure out how to pass that environment variable into your project’s containers.
For Docksal, you can simply add DOCKER_CLI_HINTS="false"
in your docksal-local.env
config file. But I realize Docksal is one of the lesser used tools that exist for this kind of development.
switool
(Switool)
April 15, 2025, 9:37am
8
they should have named the variable DOCKER_CLI_HARASS_CLIENT_TO_POTENTIALLY_MAKE_MONEY_IN_THE_FUTURE_OR_MAYBE_NOW_BECAUSE_HE_IS_TIRED_TO_SEE_THIS_MESSAGE