kubernetes/minikube

nerdctl-bin x86_64 package references wrong version variable

Open

#23,436 opened on Aug 4, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Go (5,222 forks)batch import
good first issue

Repository metrics

Stars
 (31,799 stars)
PR merge metrics
 (Avg merge 12d 19h) (43 merged PRs in 30d)

Description

Bug

In deploy/iso/minikube-iso/arch/x86_64/package/nerdctl-bin/nerdctl-bin.mk, the NERDCTL_BIN_SOURCE line references NERDCTL_BIN_AARCH64_VERSION instead of NERDCTL_BIN_VERSION:

NERDCTL_BIN_VERSION = 2.3.5
...
NERDCTL_BIN_SOURCE = nerdctl-$(NERDCTL_BIN_AARCH64_VERSION)-linux-amd64.tar.gz

It should be:

NERDCTL_BIN_SOURCE = nerdctl-$(NERDCTL_BIN_VERSION)-linux-amd64.tar.gz

Impact

This currently works by accident because both architectures use the same nerdctl version, so NERDCTL_BIN_AARCH64_VERSION resolves correctly when both packages are configured. It would break if the versions ever diverged or if the x86_64 package were built in isolation.

Fix

Change line 10 of deploy/iso/minikube-iso/arch/x86_64/package/nerdctl-bin/nerdctl-bin.mk from:

NERDCTL_BIN_SOURCE = nerdctl-$(NERDCTL_BIN_AARCH64_VERSION)-linux-amd64.tar.gz

to:

NERDCTL_BIN_SOURCE = nerdctl-$(NERDCTL_BIN_VERSION)-linux-amd64.tar.gz

Contributor guide

Research direction
Inspect the file deploy/iso/minikube iso/arch/x86 64/package/nerdctl bin/nerdctl bin.mk and confirm the variable name used on line 10. Verify where NERDCTL BIN VERSION is defined and how it is referenced for other architectures, then check for any related build configuration to ensure the substitution is correct.
Tech stack
shell
Domain
build systemdevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90