shrink / actions-docker-extract Goto Github PK

GitHub Actions now supports v20 of node, and v16 has reached EOL.

Release as new major version.

https://medium.com/prompt/package-github-actions-automatically-with-github-actions-a70b9f7bae4

• Add new main branch for v2 (leave action as-is on v1 in case anyone is relying on it)
• Release v2 from a release branch
• Protect main branch
• Protect release branch
• Change primary branch to main

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: shrink/actions-docker-extract@v1

A workflow might generate image archives: this action should take responsibility for loading these to extract from them.

Per #5 there are use-cases where someone may attempt to run this action within a container that does not have Docker: we should document the best practices for this use-case, which is described in #5 (comment) as using multiple jobs.

I try to run this example, but i got a warning in docker/build-push-action:

Warning: Unexpected input(s) 'repository', valid inputs are ['add-hosts', 'allow', 'annotations', 'attests', 'build-args', 'build-contexts', 'builder', 'cache-from', 'cache-to', 'cgroup-parent', 'context', 'file', 'labels', 'load', 'network', 'no-cache', 'no-cache-filters', 'outputs', 'platforms', 'provenance', 'pull', 'push', 'sbom', 'secrets', 'secret-envs', 'secret-files', 'shm-size', 'ssh', 'tags', 'target', 'ulimit', 'github-token']

and error in shrink/actions-docker-extract:

Unable to find image 'my-example-image:latest' locally
Error response from daemon: pull access denied for frontend, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
must specify at least one container source
Error: The process '/bin/bash' failed with exit code 1

I think it should be:

         uses: docker/build-push-action@v5 
         with: 
           tags: my-example-image:latest 

Rather than assert using test:

- run: test -e ${{ steps.extract.outputs.destination }}/001.txt || exit 1

use pr-mpt/actions-assert with a file contents assertion: prompt/assertions#19

• Replace building of test image with fixed Docker image containing a set of helpful files