Where Does Distrobox Store Config and Containers?
Distrobox reads layered config files and keeps manifests per project. The config order plus where boxes live.
Last updated
Distrobox reads config from a layered list, each level beating the last: /usr/share/distrobox/distrobox.conf, then /etc/distrobox/distrobox.conf, then ~/.config/distrobox/distrobox.conf, and finally ~/.distroboxrc. The user files decide manager, default image, and hooks.
Assemble manifests (distrobox.ini) live wherever your project is, defaulting to the current directory. The boxes themselves belong to podman or docker storage, typically ~/.local/share/containers. Exported binaries land in ~/.local/bin unless the manifest says otherwise.
Where Distrobox stores this, by platform
~/.config/distrobox/distrobox.conf
Main user config over /etc/distrobox/distrobox.conf. Manifests are per project distrobox.ini files. Box storage follows the container manager under ~/.local/share/containers.
Frequently asked questions
where is my distrobox assemble file
Wherever you ran the command: ./distrobox.ini by default, or the path passed with --file. It is a project file, not global state, so commit it with the project that needs the box.
how do i give distrobox containers custom homes
Set a per box home with --home at create time, or DBX_CONTAINER_HOME_PREFIX for a common parent. That keeps container dotfiles out of your real home while still sharing it by default.
Notice an outdated path? Let us know.