From 0460d348566db9f2d15b536688b2374d82525f72 Mon Sep 17 00:00:00 2001 From: Puneet Joshi Date: Tue, 24 Sep 2024 00:50:55 +0000 Subject: [PATCH] GITBOOK-1099: No subject --- social-registry/developer-zone/docker-packaging-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/social-registry/developer-zone/docker-packaging-guide.md b/social-registry/developer-zone/docker-packaging-guide.md index f2920401..36836ea7 100644 --- a/social-registry/developer-zone/docker-packaging-guide.md +++ b/social-registry/developer-zone/docker-packaging-guide.md @@ -39,7 +39,7 @@ Versions of all repositories that are used to create the Docker are specified in ### Creating Docker package -1. Create a package file for the new version that you want to create. The name of the package file can be arbitrary but it is recommended that it reflects the Docker tag version. E.g. `1.3.1.txt`. +1. Create a package file for the new version that you want to create. See [example](https://github.com/OpenG2P/openg2p-packaging/blob/main/packaging/packages/social-registry/1.3.1.txt). The name of the package file can be arbitrary but it is recommended that it reflects the Docker tag version. E.g. `1.3.1.txt`. 2. IMPORTANT: Update the first line in the package file for the new version. (This is critical otherwise previous tag will get overwritten on Docker Hub) 3. Inspect the contents of the package file on which versions of repositories need to be packed in this Docker. 4. Make sure the repositories are tagged with the versions matching in the package file. See above section on tagging.