Guides
Volumes
Available
This page describes what is in the code on the main branch. There are no release binaries yet.
A volume is a directory that survives redeploys. It belongs to one
namespace and environment, so test and prod never share data:
namespace = "data"
[service.db]
image = "postgres:17"
volumes = { data = "/var/lib/postgresql/data" }
namespace: data
service:
db:
image: postgres:17
volumes:
data: /var/lib/postgresql/data
The key is the volume name, the value the path inside the container. A
volume is a directory in the server's data directory, created by Podos and
bind-mounted into the container. Paths that Podos itself provides inside the
container (such as /proc, /sys and /dev) cannot be used, and two
volumes of one service cannot use the same or nested paths.
What happens to the data
- The data survives redeploys, and removing a service or an environment never deletes it by itself.
podos downkeeps the volume data on the server. A new environment with the same namespace and name finds it again.podos down --delete-volumesremoves it.
podos down --env test --delete-volumes
Volumes are not limited in size: a container can fill the data disk. Podos refuses to create containers when the data disk has less than 1 GiB or 5% of inodes free.
Backup and restore of volumes to S3 or SFTP is planned for version 0.2 (Planned · 0.2). Until then, back up volume directories with your own tools.
See volumes in the manifest reference.