Where Does Anbox Store Data on Linux?
Anbox Android runtime data root, images and snap versus classic paths.
Last updated
Anbox keeps its Android world in a data root with rootfs, overlays, containers, devices, state and logs inside. The Android image sits at the top of that tree on classic installs.
Snap builds relocate everything under snap common dirs with their own sockets. Classic builds use var lib plus run sockets. Resources and runtime inputs scatter a bit wider on both.
Where Anbox stores this, by platform
/var/lib/anbox
Data root with rootfs, overlays, containers, devices, state and logs. Android image at top on classic installs. Snap uses its own common dirs and sockets. Resources under share trees.
Frequently asked questions
Snap or classic paths?
Snap and classic installs use different roots, so match the paths to the install type first. The data root holds rootfs overlays, containers and logs together. Desktop entries live separately under applications.
Notice an outdated path? Let us know.