Repository navigation
Conversation
jirutka/setup-alpine downloads apk.static from gitlab.alpinelinux.org before it installs anything. That host has been timing out, which fails all six Alpine jobs in the setup step. Download the apk-tools-static package from dl-cdn.alpinelinux.org, which the action already uses for packages, and serve sbin/apk.static to the action from localhost, since its apk-tools-url input only accepts http(s) URLs. The package URL and the binary's SHA-256 are pinned, and the action still verifies the hash before using it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The six Alpine jobs fail in the
Setup Alpine Linuxstep before anything is built.jirutka/setup-alpine@v1downloads the staticapk.staticbinary fromgitlab.alpinelinux.org, and that host times out (curl error 28 after 10 s). This hit master on 2026-10-22 and #265 on 2026-10-28, and it fails every PR while the host is down.dl-cdn.alpinelinux.org, where the action already gets its packages, stays reachable.A new step downloads the
apk-tools-staticpackage from dl-cdn, extractssbin/apk.staticand serves it on127.0.0.1:8099. The action gets that URL through itsapk-tools-urlinput, which only acceptshttp://andhttps://URLs (notfile://), and checks the file against the pinned SHA-256 before using it. The binary is the only thing the action fetches from gitlab: QEMU and the Alpine packages already come from dl-cdn. The build and test steps are unchanged.The package is pinned to
v3.22/main/x86_64/apk-tools-static-2.14.12-r0.apk. The action deliberately stays on apk-tools 2.14.x (its default is 2.14.10), whilelatest-stablenow ships 3.0.8. x86_64 is the runner's arch; the static apk installs the target arch into the chroot as before. dl-cdn removes an old package file when Alpine updates it, so if the URL starts to 404 the URL and hash need updating, as the comment in the workflow says.Testing:
Downloading http://127.0.0.1:8099/apk.staticandapk: OK, has no gitlab requests, andmake testpasses (75 pass, 0 fail).make testpasses.