Skip to content

Commit b961f91

Browse files
FloorDjsilvela
andauthored
Apply suggestions from code review
Co-authored-by: Jaime Silvela <[email protected]> Signed-off-by: Floor Drees <[email protected]>
1 parent b49c4b5 commit b961f91

File tree

1 file changed

+2
-2
lines changed
  • content/blog/building-images-bake

1 file changed

+2
-2
lines changed

content/blog/building-images-bake/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Using the `--print` flag you can explore the full list of tags created that are
125125

126126
### Step 4: Serve the image
127127

128-
You can now let your clusters use the image that we've built based on the CloudNativePG operand images.
128+
You can now use the image that we've built for your clusters.
129129

130130
## Deep dive into the Bake and Dockerfile
131131

@@ -134,7 +134,7 @@ The simplicity of Bake to do even more stuff is amazing, and allows you to creat
134134
### Bake file
135135

136136
The magic starts with our [postgres-containers repository](https://github.com/cloudnative-pg/postgres-containers),
137-
where we have a `docker-bake.hcl` file that is being used to build the images provided by the CloudNativePG project.
137+
where we have a `docker-bake.hcl` file that is being used to build the images for the CloudNativePG project.
138138
It's the base for our custom Bake file.
139139

140140
The `docker-bake.hcl` file contains a lot of functions that are used to build the images. One of them is the `getExtensionsString()`.

0 commit comments

Comments
 (0)