Where Does Easypanel Store Apps and Data?
Easypanel stores everything under /etc/easypanel on Linux, with each service keeping its data in a projects folder per project and service.
Last updated
Easypanel follows one rule: if it matters, it is under /etc/easypanel. The install script bind-mounts that folder into the control plane, and every project and service branches from it. Learn that root and you can find anything.
Service data sits one level deeper, in a data folder per project and service. The host side is constant while the container target varies by database engine. Volume backups skip Bind and File mounts by design, which is the detail that bites people who assume everything is covered.
Where Easypanel stores this, by platform
/etc/easypanel
Install root bind-mounted into Easypanel services. Projects, service definitions and the data folders below all branch from here. Destroying a service deletes its data folder under this tree permanently.
/etc/easypanel/projects/[project]/[service]/data
Per-service persistent data on the host, with [project] and [service] replaced by your names. Postgres, MySQL and Mongo each mount this host folder to their own container data path. Bind and File mounts are excluded from volume backups.
Frequently asked questions
How do I back up Easypanel services?
Archive /etc/easypanel whole. Each service keeps a data folder at /etc/easypanel/projects/[project]/[service]/data on the host. Named volume mounts back up with the service, but Bind and File mounts are excluded, so check mount types first.
I destroyed an Easypanel service. Where did its data go?
It is gone. The docs state plainly that destroying a service deletes its /etc/easypanel/projects/.../data directory permanently. There is no trash. Snapshot the data folder before destroying anything you might want back.
Where is my Easypanel Postgres data on disk?
Look under /etc/easypanel/projects/[project]/[service]/data on the host. Postgres maps it to /var/lib/postgresql/data in the container, MySQL to /var/lib/mysql and Mongo to /data/db. The host pattern is constant while the container target changes per engine.
Notice an outdated path? Let us know.