Directories¶
This page lists the directories Dangerzone uses to store data, on each platform.
Configuration directory¶
📁 ~/Library/Application Support/dangerzone/
Same as the data directory.
📁 %LOCALAPPDATA%\dangerzone\dangerzone\
Same as the data directory.
📁 ~/.config/dangerzone/
Respects the XDG_CONFIG_HOME environment variable.
settings.json- The Dangerzone settings. See Settings.
Data directory¶
📁 ~/Library/Application Support/dangerzone/
Same as the configuration directory.
📁 %LOCALAPPDATA%\dangerzone\dangerzone\
Same as the configuration directory.
📁 ~/.local/share/dangerzone/
Respects the XDG_DATA_HOME environment variable.
signatures/- The signatures of the sandbox images that Dangerzone has verified, grouped by the digest of the public key that signed them. See Independent sandbox updates.
signatures/last_log_index- The Rekor transparency log index of the installed sandbox image. Dangerzone uses it to refuse older images, and considers the sandbox image as not installed if this file is missing.
Cache directory¶
📁 ~/Library/Caches/dangerzone/
📁 %LOCALAPPDATA%\dangerzone\dangerzone\Cache\
📁 ~/.cache/dangerzone/
Respects the XDG_CACHE_HOME environment variable. Dangerzone does not use this directory on Linux.
Dangerzone regenerates these files as needed, so you can safely delete them.
containers.conf- The Podman configuration that Dangerzone passes to its bundled Podman via the
CONTAINERS_CONFenvironment variable. It is rewritten whenever Dangerzone runs. shared/seccomp.gvisor.json- A copy of the seccomp profile of the sandbox. Dangerzone mounts the cache directory read-only into the Podman machine, so that the profile can reach the container.