Skip to content

Commit

Permalink
WIP - removing details
Browse files Browse the repository at this point in the history
Signed-off-by: Juan Bustamante <[email protected]>
  • Loading branch information
jjbustamante committed Sep 18, 2023
1 parent 37e6c26 commit 3f689d5
Showing 1 changed file with 9 additions and 5 deletions.
14 changes: 9 additions & 5 deletions text/0000-multiarch-builders-and-package.md
Original file line number Diff line number Diff line change
Expand Up @@ -198,7 +198,7 @@ On the other hand, when a user exports the buildpack package into the docker dae
pack buildpack package my-buildpack --config ./package.toml
```

`pack` will not be able to create the [image index](https://github.com/opencontainers/image-spec/blob/master/image-index.md) and it will export the buildpack that corresponds to the `host` machine `os/arch`
`pack` will not be able to create the [image index,](https://github.com/opencontainers/image-spec/blob/master/image-index.md) and it will export the buildpack that corresponds to the `host` machine `os/arch`

<!--
- `pack` will determine the `host` machine `os/arch`
Expand All @@ -211,7 +211,7 @@ pack buildpack package my-buildpack --config ./package.toml
-->
## Buildpack Builder

In case of packaing a *Builder*, we assume the buildpack authors migrated their `builder.toml` and [remove the stack](https://github.com/buildpacks/pack/issues/1303) concept.
In case of packing a *Builder*, we assume the buildpack authors migrated their `builder.toml` and [remove the stack](https://github.com/buildpacks/pack/issues/1303) concept.

A sample `builder.toml` file looks like:

Expand All @@ -230,15 +230,19 @@ image = "docker.io/paketobuildpacks/build-jammy-tiny:0.2.3"
#### Package a multi-arch builder and publish it to a registry

```bash
pack builder create my-jammy-builder --config ./builder.toml --platform "linux/amd64" --platform "linux/arm64" --publish
pack builder create my-jammy-builder --config ./builder.toml \
--platform "linux/amd64" \
--platform "linux/arm64" \
--publish
```

In this case:

`pack` will follow the builder creating process for each provided platform, `build` and `run` images and declared `buildpacks` must be addressable by an [image index](https://github.com/opencontainers/image-spec/blob/master/image-index.md)

`pack` will follow the builder creation process for **each provided platform**, and each platform corresponds to a different builder image that is exported into a [image index](https://github.com/opencontainers/image-spec/blob/master/image-index.md)

<!--
and every `build`, `run` images and declared `buildpacks` must be addressable by an [image index](https://github.com/opencontainers/image-spec/blob/master/image-index.md)
This provides a high level overview of the feature.
- Define any new terminology.
Expand Down

0 comments on commit 3f689d5

Please sign in to comment.