CrazyMax
CrazyMax
Ok found the issue. Looks like this error is triggered when there is a new update available.
Can you try the artifact available at https://github.com/portapps/whatsapp-portable/actions/runs/2093325874 and let me know?
We could have a `args` input. Would look like this: ```yaml - name: Scan for vulnerabilities uses: crazy-max/ghaction-container-scan@v2 with: image: user/app:latest args: | --security-checks vuln --ignore-unfixed ```
Hum yeah that might be an issue with the container scanner. Can you try with: ```yml - name: Build and push uses: docker/[email protected] with: files: | ./docker-bake.hcl ${{ steps.docker_meta.outputs.bake-file }}...
> avoid building for amd64 in this instance just to scan it and then throw it away. Yeah you right, we might need a multi exporter on BuildKit to handle...
@glours Looks like [2.1.1](https://github.com/compose-spec/compose-go/releases/tag/v2.1.1) is out, can you bump to this version instead? Thanks.
> Hahah @crazy-max I just see your message, is it too late to bump the version? No worries I bumped it myself, see last commit.
I started to work on it by evaluating contexts and adding strict schema validation for `group` and `target` block but there might be breaking changes if we introduce such validation....
As discussed print a warning in the meantime.
> but HCL is very limiting. Can you elaborate on these limitations?