Adding some context for the FUNC_REGISTRY variable and highlighting the fact that the prompt asks for an image registry (#5677)

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
This commit is contained in:
Matthias Wessendorf 2023-09-12 10:36:24 +02:00 committed by GitHub
parent 02b135d4be
commit 803942b55e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 1 deletions

View File

@ -2,7 +2,7 @@
- /docs/getting-started/build-run-deploy-func.md
- /docs/functions/building-functions.md
-->
The `build` command uses the project name and the image registry name to construct a fully qualified container image name for the function. If the function project has not previously been built, you are prompted to provide an image registry.
The `build` command uses the project name and the image registry name to construct a fully qualified container image name for the function. If the function project has not previously been built, you are prompted to provide an **image registry**.
=== "func"
@ -19,3 +19,6 @@ The `build` command uses the project name and the image registry name to constru
```bash
kn func build
```
!!! note
The coordinates for the **image registry** can be configured through an environment variable (`FUNC_REGISTRY`) as well.

View File

@ -16,6 +16,9 @@ The `run` command builds an image for your function if required, and runs this i
func run [--registry <registry>]
```
!!! note
The coordinates for the **image registry** can be configured through an environment variable (`FUNC_REGISTRY`) as well.
Using this command also builds the function if necessary.
You can force a rebuild of the image by running the command: