Where Is the dive Config File?
dive YAML config in your home directory, and which registries and behaviors it controls.
Last updated
dive reads an optional .dive.yaml file from your home directory. No file means defaults: Docker Hub registry, standard efficiency thresholds and stock key bindings. Everything the file controls also has a flag equivalent, so casual use never needs it.
The file earns its keep for private registries and permanent taste. CI pipelines and air gapped setups pin registry credentials and thresholds there, while daily drivers tweak bindings once and forget them. Keep it in dotfiles if you live in containers; otherwise the defaults are fine.
Where dive stores this, by platform
~/.dive.yaml
YAML format in home, not under .config. Holds container engine choice, registry settings, efficiency rules and key bindings. Missing file always means defaults, never an error.
~/.dive.yaml
Same home directory file as Linux. Docker Desktop users share one config across CLI contexts, since dive reads the file independently of which engine endpoint is active.
%USERPROFILE%\.dive.yaml
Same dotfile in %USERPROFILE% rather than AppData. The home directory convention holds across all three platforms, so one file copies between them untouched.
Frequently asked questions
how do i reset dive settings
Delete .dive.yaml from home and relaunch dive. Built in defaults return immediately, clearing bad registry settings, broken key bindings and stuck UI options.
how do i move dive config to a new computer
Copy .dive.yaml to the new machine's home directory. It holds registry choice, lowest efficiency threshold and key bindings in one portable file with no machine specific paths.
Notice an outdated path? Let us know.