Skip to content
New issue

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

Attempting to run tests via act fails to build the container #81

Open
chuckwondo opened this issue Aug 8, 2024 · 1 comment
Open

Attempting to run tests via act fails to build the container #81

chuckwondo opened this issue Aug 8, 2024 · 1 comment
Labels
bug Something isn't working stale Awaiting input from creator for prolonged time period

Comments

@chuckwondo
Copy link

Describe the bug:

Running act -b -j build fails as follows:

$ 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:

  • Host Machine OS (Windows/Linux/Mac): Mac
  • Browser (Chrome/Firefox/Safari): N/A

Possible Fix:

Additional context:

$ act --version
act version 0.2.64
@chuckwondo chuckwondo added the bug Something isn't working label Aug 8, 2024
Copy link
Contributor

github-actions bot commented Nov 7, 2024

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

@github-actions github-actions bot added the stale Awaiting input from creator for prolonged time period label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Awaiting input from creator for prolonged time period
Projects
None yet
Development

No branches or pull requests

1 participant