ConceptsBuilds & runtimes
Images and retention
Each deploy has its own image. Ferry keeps the newest images and deletes the older ones.
Each build makes one image for its deploy.
1 / 4
The tag of an image
Each build makes an image with the tag <prefix>/<service>:<deploy-id>. Ferry also puts a label on it, to know its service.
What Ferry keeps
- The 5 newest images of the service.
--keep-imageson ferryd sets this number. - The image of the live deploy, at any age.
- The images of the deploys in progress, at any age.
If the image of a deploy is gone
You cannot roll back to that deploy. Deploy again from the source.
A rollback and a restart use the images that Ferry keeps.
Ferry deletes only the images that it gave a tag to for the service. It never deletes an image that you pulled, or a public base image.
Ferry pulls the image, then gives it the same form of tag. This is the pinned image. Thus each deploy refers to the exact image that it ran.
Ferry deletes all its images.