catthehacker/ubuntu:act-latest should contain node

[till]

I realize the images are not meant to be complete, etc. but since node is somewhat required for a lot of github actions, would it be possible to include node?

I usually get by with node:16-buster-slim but that seems to require a TLS update, I think:

| source: source#getRelease
| -----------------
| ERROR: 	Post "https://api.github.com/graphql": tls: failed to verify certificate: x509: certificate signed by unknown authority
| ERROR: ✗ Post "https://api.github.com/graphql": tls: failed to verify certificate: x509: certificate signed by unknown authority
| 
| ERROR: something went wrong in "target#download" : update pipeline: template: cfg:18:88: executing "cfg" at <source "getRelease">: error calling source: parent source "getRelease" failed

(I am using act to run a workflow that invokes updatecli.io.)

[ChristopherHX]

Did node really disappear randomly from the catthehacker/ubuntu:act-latest image? every default image always contains node, if it doesn't something weird is going on.

Please Provide me the digest for that image to look into the one you have installed, that tag is rolling use something like docker image inspect catthehacker/ubuntu:act-latest and post the result.

In very rare cases docker rmi catthehacker/ubuntu:act-latest together with pulling the image again can help to resolve inconsitency that is not part of the image itself. The digest of your local copy helps me to download the exact same image that you have.

[bnthn]

I had quite a hard time today trying to get my Gitea build pipeline up and running again after updating the Act Runner docker image from 2.5 to 2.11. It said OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown when trying to execute any action, which is weird because the cth image didn't change i suppose.

After removing the image with docker rmi catthehacker/ubuntu:act-latest and let it get pulled again by the pipeline did the trick.

[ELY3M]

I am having same issue!!!! I am using gitea with gitea-runner on ubuntu.

with:
persist-credentials: false
OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH
Error: Process completed with exit code 127.

I am using this image

ghcr.io/catthehacker/ubuntu:full-latest