fix: unexport AddInitrdRecord and clean up error formatting

[hemang1404]

Related issues

• Fixes Unexport internal function AddInitrdRecord #502

Description

Unexported the internal helper function AddInitrdRecord by renaming it to addInitrdRecord. Cleaned up the error strings in the file by lowercasing them and using %w standard error wrapping formats.

How was this tested?

Verified that the package successfully compiles locally by compiling against the target Linux architecture ($env:GOOS="linux"; go build ./pkg/unikontainers/initrd/...).

LLM usage

Used chatgpt to verify changes

Checklist

• I have read the contribution guide.
• The linter passes locally (make lint).
• The e2e tests of at least one tool pass locally (make test_ctr, make test_nerdctl, make test_docker, make test_crictl).
• If LLMs were used: I have read the llm policy.

[netlify]

✅ Deploy Preview for urunc canceled.

Name	Link
🔨 Latest commit	bbd8ca2
🔍 Latest deploy log	https://app.netlify.com/projects/urunc/deploys/69d4e84f3b077a0008063046

[cmainas]

Thank you @hemang1404 for this PR.

Is there any particular reason for not running the tests, or at least the linter?

[hemang1404]

Hi @cmainas, I ran the unit tests locally and all the checks passed but I noticed that make lint was failing on my branch due to a pre-existing indentation issue in a different file (pkg/unikontainers/hypervisors/qemu.go.

After fixing the indentation issue there, make lint passes successfully.

[cmainas]

I see, we need to check why it fails locally and not in our CI. The linter warning is valid though.

[IrvingMg]

I see, we need to check why it fails locally and not in our CI. The linter warning is valid though.

I looked into the issue, and it seems CI doesn’t report it because the only-new-issues flag is enabled in the workflow:

urunc/.github/workflows/lint.yml

Line 47 in 6df97b4

only-new-issues: true

As I understand it, this flag filters issues based on the diff. Since there are no new changes touching the problematic code, the issue isn’t reported in CI.

Locally, however, the make lint target doesn’t use this filter, which is why the issue shows up.

Yet, using only-new-issues seems to be the standard approach, so my suggestion would be to just fix the formatting issue and keep only-new-issues as is.