Resolve latest-stable before caching downloaded assets #44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finding:
The default download path caches assets under the moving Alpine alias
latest-stable, and the run path later regenerates the kernel cmdline from that alias.Problem:
src/utils.zigsetsdefault_version = "latest-stable"and buildsalpine_repo={base_url}/{version}/main.src/cmd_download.zigwrites the downloaded kernel/initrd into~/Library/Application Support/vmz/<version>/.latest-stablepoints at one Alpine release and boots after the alias moves, the cached kernel/initrd can be paired with a newer repository URL.Impact:
This can create hard-to-reproduce boot or package failures after Alpine releases, because the local cache name does not capture the concrete release it came from.
Suggested fix:
Resolve
latest-stableto a concretev3.xrelease at download time, store assets under that concrete release, and either keep alias metadata or refresh the alias explicitly. The run path should use the same resolved repo URL that matched the downloaded assets.Relevant code:
src/utils.zig: default version and default command line.src/cmd_download.zig: download URL and destination directory.