USE_LATEST_BUILT_KERNEL=yes is broken
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 131
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
Looks like USE_LATEST_BUILT_KERNEL=yes is broken. I suspect this is because we moved to ghcr.io from quay.io.
❯ ./build.sh build hook-latest-lts-amd64 USE_LATEST_BUILT_KERNEL=yes
🌿 [info ] Applying cmdline param to environment 'USE_LATEST_BUILT_KERNEL': '(unset)' --> 'yes'
🌿 [info ] Using Hook version (HOOK_VERSION): 0.11.1
🌿 [info ] All deps found, no apt installs necessary on host.
🌿 [info ] Current Docker context ('default') socket: 'unix:///var/run/docker.sock'
🌿 [info ] Command (first argument): explicitely set to 'build'
🌿 [info ] Kernel/flavor ID (second argument): explicitely set to 'hook-latest-lts-amd64'
jq: error (at <stdin>:1): Cannot iterate over null (null)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with build.sh and reproduce the issue using the reported hook-latest-lts-amd64 command with USE_LATEST_BUILT_KERNEL=yes. Trace the jq input used for the latest built kernel and compare the ghcr.io and quay.io references mentioned in the report. Done means the command completes without the jq null error and selects the latest built kernel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100