Skip to content

Commit 19edf8c

Browse files
committed
update with suggestions
Signed-off-by: Daniel Chambre <[email protected]>
1 parent 078791f commit 19edf8c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/blog/customizing-hcl/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,18 +27,18 @@ The other week [Jonathan Gonzalez]({{% ref "/authors/jgonzalez/" %}}) wrote an
2727
on how to customize docker images using an override hcl file.
2828
Before the [postgres-containers repo]((https://github.com/cloudnative-pg/postgres-containers))
2929
was extended by the option to build the images with `docker build bake`,
30-
I had to do this steps, for each PostgreSQL version.
30+
I had to do this steps manually in order to have custom images for our workloads.
3131

3232
- clone the repo
3333
- edit the dockerfile
3434
- build the image
3535
- push it to the registry
3636

37+
Edit, build and push had to be done for each PostgreSQL version.
3738
So a lot of boring work needed to be done in order to have updated images.
3839
The chance to avoid this work sounds prommising to me, so I started with the
3940
[hcl file]((https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg.github.io/refs/heads/main/content/blog/building-images-bake/bake.hcl))
40-
41-
The wrote and adopted it to fit my needs.
41+
Jonathan wrote and adopted it to fit my needs.
4242
After a troubleshooting session, he asked me to share the changes I made.
4343
So here we are.
4444

@@ -149,7 +149,7 @@ We can now build the image using the following command:
149149
docker buildx bake -f docker-bake.hcl -f cwd://bake.hcl "https://github.com/cloudnative-pg/postgres-containers.git" myimage
150150
```
151151

152-
### Step 3: Use them
152+
### Step 3: Use it
153153

154154
The only missing step to use the images is to update your
155155
[Image Catalog / Cluster Image Catalog]((https://cloudnative-pg.io/documentation/current/image_catalog/))

0 commit comments

Comments
 (0)