cloudposse / cloudposse/github-action-docker-build-push
Add An Input To Set Docker Buildx version
- Lingua principale
- Dockerfile
- Stelle
- 14
- Fork
- 15
- Merge medio
- 12m
- PR unite (30g)
- 2
Descrizione
Have a question? Please checkout our [Slack Community](https://slack.cloudposse.com) or visit our [Slack Archive](https://archive.sweetops.com/).
[](https://slack.cloudposse.com)
## Describe the Feature
Ability to provide a buildx version so when setting `provenance: false` it is not ignored.
## Expected Behavior
Expect a buildx version to be set so provenance: false is recognized and multiple format image is not pushed to ecr.
## Use Case
This Current version of build-push action pushes muilti platform multi-image/image index types to ecr. Due to AWS Lambda not supporting image index artifact type I need to turn off multi image. When I set `provenance: false` it is ignored because a buildx version is not provided and no default is set. buildx version states unknown


## Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Provide an input that sets the buildx version
## Alternatives Considered
Explain what alternative solutions or features you've considered.
I have added steps in the workflow that set buildx version before calling the build push action.

## Additional Context
Add any other context or screenshots about the feature request here.
Created an issue on docker build-push github repo: https://github.com/docker/build-push-action/issues/1035
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inspect the action's input definitions and the Docker Buildx setup entry point, then trace how the provenance option is passed to the build. Add an input for selecting the Buildx version and verify that setting it allows provenance: false to be honored and prevents a multi-platform image index from being pushed to ECR.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, github-actions
- Ambito
- ci-cd, devops
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100