From 2e64438fedf0c2484a2c8b184e358f6fe9423d73 Mon Sep 17 00:00:00 2001 From: Sarah Jamie Lewis Date: Wed, 18 Jan 2023 11:55:00 -0800 Subject: [PATCH] Updates --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ce7a859..caf7b55 100644 --- a/README.md +++ b/README.md @@ -49,8 +49,8 @@ These are temporary disk images that are used while repliqate is running. By def We do use Docker as part of our continuous build processes. However, we have chosen to develop repliqate to meet two specific requirements: -1. Standlone and Unprivileged - [Docker requires a whole host of permissions](https://docs.docker.com/engine/install/linux-postinstall/) to be granted, and privileged services to be setup, in order for containers to be run by non-root users. Our goal with repliqate was to provide a standalone way of reproducing builds. -2. Redundancy - Having a tool that is entirely separate from our build containers (and the Docker infrastructure that supports them) allows us have both keep each other in check. +1. Standlone and Unprivileged - Our goal with repliqate was to provide a standalone way of reproducing builds. [Docker requires a whole host of permissions](https://docs.docker.com/engine/install/linux-postinstall/) to be granted, and privileged services to be setup, in order for containers to be run by non-root users. +2. Redundancy - Having a tool that is entirely separate from our build containers (and the Docker infrastructure that supports them) allows us have both keep each other in check. Many of the containers we rely on in our build process are managed and maintained by other teams. By maintaining our own reproducible build scripts we can narrow down the exact environments needed while still taking advantage of open source infrastructure for our day-to-day builds. ### Builds are slow. Can they be sped up?