Closed iapicca closed 2 years ago
OCI and bud
are orthagonal. you can 'build using docker' and get an image with OCI metadata.
If you want to use buildah build
then do not set the containerfiles
input
If you want to use a custom script, then this action is not for you - just run your script.
closing pending any new questions.
Version
redhat-actions/buildah-build@v2
Describe the bug
(I'm a noob and it's probably my fault)
setting
oci: true
in the workflow runsbuildah bud
and notbuildah build
anywaySteps to reproduce, workflow links, screenshots
workflow
```yaml name: Test image on: pull_request: jobs: test_build: name: test build runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: redhat-actions/buildah-build@v2 with: image: test-image tags: v1 ${{ github.sha }} oci: true containerfiles: | ./build.sh ```logs
```console Run redhat-actions/buildah-build@v2 /usr/bin/buildah version Overriding storage mount_program with "fuse-overlayfs" in environment Performing build from Containerfile /usr/bin/buildah bud -f /home/runner/work/flutter_development_container/flutter_development_container/build.sh --format oci -t test-image:v1 /home/runner/work/flutter_development_container/flutter_development_container no FROM statement found time="2021-10-11T19:14:36Z" level=error msg="exit status 125" Error: Error: buildah exited with code 125 no FROM statement found time="2021-10-11T19:14:36Z" level=error msg="exit status 125" ```#
if you want to look at the repo here is the link, I'm really new to devops stuff so please understand (also if you want to help me out I'd be very happy :) )