mirror of
https://github.com/redhat-actions/buildah-build.git
synced 2025-04-20 09:01:23 +00:00
Update README
Signed-off-by: divyansh42 <diagrawa@redhat.com>
This commit is contained in:
parent
524995d2e1
commit
493195bb52
1 changed files with 13 additions and 10 deletions
23
README.md
23
README.md
|
@ -25,10 +25,8 @@ After building your image, use [push-to-registry](https://github.com/redhat-acti
|
||||||
|
|
||||||
| Input Name | Description | Default |
|
| Input Name | Description | Default |
|
||||||
| ---------- | ----------- | ------- |
|
| ---------- | ----------- | ------- |
|
||||||
| arch | Label the image with this architecture, instead of defaulting to the host architecture. Refer to [Multi arch builds](#multi-arch-builds) for more information. | None (host architecture)
|
| archs | Label the image with this architecture, instead of defaulting to the host architecture. Refer to [Multi arch builds](#multi-arch-builds) for more information. For multiple architectures, seperate them by a comma | None (host architecture)
|
||||||
| archs | Same as input `arch`, use this for multiple architectures. Seperate them by a comma | None (host architecture)
|
| platforms | Label the image with this platform, instead of defaulting to the host platform. Refer to [Multi arch builds](#multi-arch-builds) for more information. For multiple platforms, seperate them by a comma | None (host platform)
|
||||||
| platform | Label the image with this platform, instead of defaulting to the host platform. Refer to [Multi arch builds](#multi-arch-builds) for more information. | None (host platform)
|
|
||||||
| platforms | Same as input `platform`, use this for multiple platforms. Seperate them by a comma | None (host platform)
|
|
||||||
| build-args | Build arguments to pass to the Docker build using `--build-arg`, if using a Containerfile that requires ARGs. Use the form `arg_name=arg_value`, and separate arguments with newlines. | None
|
| build-args | Build arguments to pass to the Docker build using `--build-arg`, if using a Containerfile that requires ARGs. Use the form `arg_name=arg_value`, and separate arguments with newlines. | None
|
||||||
| context | Path to directory to use as the build context. | `.`
|
| context | Path to directory to use as the build context. | `.`
|
||||||
| containerfiles\* | The list of Containerfile paths to perform a build using docker instructions. Separate filenames by newline. | **Required**
|
| containerfiles\* | The list of Containerfile paths to perform a build using docker instructions. Separate filenames by newline. | **Required**
|
||||||
|
@ -47,8 +45,7 @@ After building your image, use [push-to-registry](https://github.com/redhat-acti
|
||||||
|
|
||||||
| Input Name | Description | Default |
|
| Input Name | Description | Default |
|
||||||
| ---------- | ----------- | ------- |
|
| ---------- | ----------- | ------- |
|
||||||
| arch | Label the image with this architecture, instead of defaulting to the host architecture. Refer to [Multi arch builds](#multi-arch-builds) for more information. | None (host architecture)
|
| archs | Label the image with this architecture, instead of defaulting to the host architecture. Refer to [Multi arch builds](#multi-arch-builds) for more information. For multiple architectures, seperate them by a comma | None (host architecture)
|
||||||
| archs | Same as input `arch`, use this for multiple architectures. Seperate them by a comma | None (host architecture)
|
|
||||||
| base-image | The base image to use for the container. | **Required**
|
| base-image | The base image to use for the container. | **Required**
|
||||||
| content | Paths to files or directories to copy inside the container to create the file image. This is a multiline input to allow you to copy multiple files/directories.| None
|
| content | Paths to files or directories to copy inside the container to create the file image. This is a multiline input to allow you to copy multiple files/directories.| None
|
||||||
| entrypoint | The entry point to set for the container. Separate arguments by newline. | None
|
| entrypoint | The entry point to set for the container. Separate arguments by newline. | None
|
||||||
|
@ -200,16 +197,22 @@ sudo podman run --rm --privileged docker.io/tonistiigi/binfmt --install all
|
||||||
```
|
```
|
||||||
This registration remains active until the host reboots.
|
This registration remains active until the host reboots.
|
||||||
|
|
||||||
### The `arch` and `platform` inputs
|
### The `archs` and `platforms` inputs
|
||||||
The `arch` and `platform` arguments override the Architecture and Platform labels in the output image, respectively. They do not actually affect the architectures and platforms the output image will run on. The image must still be built for the required architecture or platform.
|
|
||||||
|
The `archs` and `platforms` arguments override the Architecture and Platform labels in the output image, respectively. They do not actually affect the architectures and platforms the output image will run on. The image must still be built for the required architecture or platform.
|
||||||
|
|
||||||
There is a simple example [in this issue](https://github.com/redhat-actions/buildah-build/issues/60#issuecomment-876552452).
|
There is a simple example [in this issue](https://github.com/redhat-actions/buildah-build/issues/60#issuecomment-876552452).
|
||||||
|
|
||||||
### Creating a Multi-Arch Image List
|
### Creating a Multi-Arch Image List
|
||||||
Input `archs` and `platforms` is provided to build the multi architecture images. If one of these input is provided then a manifest is built with the multiple architecture images. Name of the manifest is taken from the inputs `image` and `tags`.
|
|
||||||
|
Input `archs` and `platforms` is provided to build the multi architecture images. If one of these input is provided then a [manifest](https://github.com/containers/buildah/blob/main/docs/buildah-manifest.1.md) is built with the multiple architecture images. Name of the manifest is taken from the inputs `image` and `tags`.
|
||||||
Incase multiple tags are provided then multiple manifest is created based on the provided tags.
|
Incase multiple tags are provided then multiple manifest is created based on the provided tags.
|
||||||
|
|
||||||
[`push-to-registry`](https://github.com/redhat-actions/push-to-registry) action can be used to push the generated manifest.
|
Use the `archs` and `platforms` inputs to build multi-architecture images. The name of the manifest is determined by the image and tags inputs.
|
||||||
|
|
||||||
|
If multiple tags are provided, multiple equivalent manifests will be created with the given tags.
|
||||||
|
|
||||||
|
[`push-to-registry`](https://github.com/redhat-actions/push-to-registry) action can be used to push the generated image manifest.
|
||||||
|
|
||||||
## Build with docker/metadata-action
|
## Build with docker/metadata-action
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue