jq not found #312

New Issue

prologic · 2023-07-29T06:12:27Z

prologic commented

2023-07-29 06:12:27 +00:00

Trying to run an action that requires jq results in:

jq not found, please install it, https://stedolan.github.io/jq/download/

I could install this fairly easily, but it might be nice to include this in the default runner image?

Trying to run an action that requires `jq` results in: ``` jq not found, please install it, https://stedolan.github.io/jq/download/ ``` I _could_ install this fairly easily, but it might be nice to include this in the default runner image?

lunny commented

2023-07-29 08:42:58 +00:00

You can build your own images. Currently, the default image is very small.

prologic commented

2023-07-29 08:43:45 +00:00

Any instructions for doing this and reconfiguring act_runner to use the custom image?

Any instructions for doing this and reconfiguring `act_runner` to use the custom image?

ednxzu commented

2023-07-29 17:56:33 +00:00

Just build docker images from node or from whatever else you want. Publish it to a registry (public or private)

To use custom images (might need to re-register the runner)https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L32-L36

To override images implied by labels:

---
name: test
on: [push]

jobs:
  lint:
    name: Linting
    runs-on: ubuntu-latest
    container:
      image: your_image:<tag>
      credentials: # if needed 
        username: ${{ secrets.ACTIONS_USER }}
        password: ${{ secrets.ACTIONS_TOKEN }}
    steps:
      - name: Checkout
        uses: actions/checkout@v3
   ...

Just build docker images from node or from whatever else you want. Publish it to a registry (public or private) To use custom images (might need to re-register the runner)https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L32-L36 To override images implied by labels: ``` --- name: test on: [push] jobs: lint: name: Linting runs-on: ubuntu-latest container: image: your_image:<tag> credentials: # if needed username: ${{ secrets.ACTIONS_USER }} password: ${{ secrets.ACTIONS_TOKEN }} steps: - name: Checkout uses: actions/checkout@v3 ... ```

👍 1

prologic commented

2023-07-30 01:20:11 +00:00

Thanks!

prologic commented

2023-07-30 01:32:27 +00:00

One final question, please link to where the official image is used now? I assume that's hard-coded in the code somewhere (with no special configuration of the runner in play)

One final question, please link to where the official image is used now? I assume that's hard-coded in the code somewhere (_with no special configuration of the runner in play_)

techknowlogick commented

2023-07-30 19:04:55 +00:00

One final question, please link to where the official image is used now? I assume that's hard-coded in the code somewhere (with no special configuration of the runner in play)

the default image used is node:18 (IIRC), it's set by the labels on registration. The minimum required image to run most actions is one that has nodejs 16, although some actions may assume other binaries present that arent.

You can see more details about images in use here: https://github.com/nektos/act/blob/master/IMAGES.md note that there is a "full" image that has most/all of whats in the Github action VM, but it is quite large.

> One final question, please link to where the official image is used now? I assume that's hard-coded in the code somewhere (with no special configuration of the runner in play) the default image used is node:18 (IIRC), it's set by the labels on registration. The minimum required image to run most actions is one that has nodejs 16, although some actions may assume other binaries present that arent. You can see more details about images in use here: https://github.com/nektos/act/blob/master/IMAGES.md note that there is a "full" image that has most/all of whats in the Github action VM, but it is quite large.

👍 1

techknowlogick closed this issue

2023-07-30 19:04:55 +00:00

Sign in to join this conversation.

No Milestone

No Assignees

4 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act_runner#312