From 6575648f069f8f7aa7f72ec2b0e38b77914f2883 Mon Sep 17 00:00:00 2001 From: Mark Lodato Date: Thu, 27 Jan 2022 13:23:25 -0500 Subject: [PATCH] README: fix link to race conditions (#1367) * Use correct HTML anchor. * Use the term "race condition" consistently to make it easier to find. (Previously it used "race" in one and "racy" in the other, making it difficult to do a find/grep.) Signed-off-by: Mark Lodato --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9a721dd7c5d..b8412136199 100644 --- a/README.md +++ b/README.md @@ -383,7 +383,7 @@ or garbage-collected when the image is deleted. Similarly, they **can** easily be copied from one environment to another, but this is not automatic. -Multiple signatures are stored in a list which is unfortunately "racy" today. +Multiple signatures are stored in a list which is unfortunately a race condition today. To add a signature, clients orchestrate a "read-append-write" operation, so the last write will win in the case of contention. @@ -436,7 +436,7 @@ on the sha256 of what we're signing) for locating the signature index. Roughly (ignoring ports in the hostname): `s/:/-/g` and `s/@/:/g` to find the signature index. -See [Race conditions](#race-conditions) for some caveats around this strategy. +See [Race conditions](#registry-details) for some caveats around this strategy. Alternative implementations could use transparency logs, local filesystem, a separate repository registry, an explicit reference to a signature index, a new registry API, grafeas, etc.