We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
act
Describe the bug:
Running act -b -j build fails as follows:
act -b -j build
$ act -b -j build INFO[0000] Using docker host 'unix:///var/run/docker.sock', and daemon socket 'unix:///var/run/docker.sock' [build-pipeline/build] 🚀 Start image=catthehacker/ubuntu:act-latest [build-pipeline/build] 🐳 docker pull image=catthehacker/ubuntu:act-latest platform= username= forcePull=true [build-pipeline/build] 🐳 docker create image=catthehacker/ubuntu:act-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [build-pipeline/build] 🐳 docker run image=catthehacker/ubuntu:act-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [build-pipeline/build] ⭐ Run Main set-input-build-args [build-pipeline/build] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/0] user= workdir= [build-pipeline/build] ✅ Success - Main set-input-build-args [build-pipeline/build] ⚙ ::set-env:: BUILD_ARGS= [build-pipeline/build] ⭐ Run Main set-input-working-directory [build-pipeline/build] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1] user= workdir= [build-pipeline/build] ✅ Success - Main set-input-working-directory [build-pipeline/build] ⚙ ::set-env:: WORKING_DIRECTORY= [build-pipeline/build] ⭐ Run Main set-host-ip [build-pipeline/build] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2] user= workdir= [build-pipeline/build] ✅ Success - Main set-host-ip [build-pipeline/build] ⚙ ::set-env:: _HOST_IP=192.168.65.3 [build-pipeline/build] ⭐ Run Main actions/checkout@v2 [build-pipeline/build] ✅ Success - Main actions/checkout@v2 [build-pipeline/build] ⭐ Run Main run-build-scripts [build-pipeline/build] 🐳 docker build -t act-github-actions-build-environment-dockeraction:latest /Users/charlie/src/chuckwondo/lazydocs/.github/actions/build-environment/ [build-pipeline/build] 🐳 docker pull image=act-github-actions-build-environment-dockeraction:latest platform= username= forcePull=false [build-pipeline/build] 🐳 docker create image=act-github-actions-build-environment-dockeraction:latest platform= entrypoint=[] cmd=[] network="container:act-build-pipeline-build-204bc7dcf518e94b319efa5333933555e09951350edb67061750c9b53102ca14" [build-pipeline/build] 🐳 docker run image=act-github-actions-build-environment-dockeraction:latest platform= entrypoint=[] cmd=[] network="container:act-build-pipeline-build-204bc7dcf518e94b319efa5333933555e09951350edb67061750c9b53102ca14" | json: cannot unmarshal array into Go value of type types.ContainerJSON | jq: error (at <stdin>:1): Cannot iterate over null (null) | json: cannot unmarshal array into Go value of type types.ContainerJSON | jq: error (at <stdin>:1): Cannot iterate over null (null) [build-pipeline/build] ❌ Failure - Main run-build-scripts [build-pipeline/build] exit with `FAILURE`: 5 [build-pipeline/build] 🏁 Job failed Error: Job 'build' failed
Expected behaviour:
Build should succeed.
Steps to reproduce the issue:
Run act -b -j build
Technical details:
Possible Fix:
Additional context:
$ act --version act version 0.2.64
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days
Sorry, something went wrong.
No branches or pull requests
Describe the bug:
Running
act -b -j build
fails as follows:Expected behaviour:
Build should succeed.
Steps to reproduce the issue:
Run
act -b -j build
Technical details:
Possible Fix:
Additional context:
The text was updated successfully, but these errors were encountered: