Skip to content

Commit 235c306

Browse files
author
Natalie Arellano
committed
Clarify registry namespace and remove var
Signed-off-by: Natalie Arellano <[email protected]>
1 parent 319eea6 commit 235c306

File tree

1 file changed

+4
-11
lines changed

1 file changed

+4
-11
lines changed

content/docs/extension-author-guide/create-extension/why-dockerfiles.md

Lines changed: 4 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,24 +29,17 @@ The buildpack tries to use `tree` at build-time, and defines a launch process ca
2929

3030
### Create a builder with extensions and publish it
3131

32-
Ensure you are authenticated with an OCI registry: `docker login` should succeed
32+
For now, it is necessary for the builder image to be pushed to an OCI registry for builds with image extensions to succeed.
3333

34-
For test purposes, you can launch a local unauthenticated registry:
34+
For demo purposes, we will launch a local unauthenticated registry:
3535

3636
<!-- test:exec -->
3737
```bash
3838
docker run -d --rm -p 5000:5000 registry:2
3939
```
4040

41-
Set your preferred registry namespace (typically your username if using Docker Hub): `registry_namespace=<your preferred registry namespace>`
42-
* For now, it is necessary for the builder to be pushed to a registry for builds with image extensions to succeed
43-
44-
If using a test registry:
45-
46-
<!-- test:exec -->
47-
```bash
48-
registry_namespace=localhost:5000
49-
```
41+
You can push the builder to any registry of your choice - just ensure that `docker login` succeeds and replace `localhost:5000` in the following examples with your registry namespace -
42+
e.g., `index.docker.io/<username>`.
5043

5144
Create the builder:
5245

0 commit comments

Comments
 (0)