Bump alpine from 3.18 to 3.20 in /package

[dependabot]

Bumps alpine from 3.18 to 3.20.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[brandond]

k3s/package/Dockerfile

Line 5 in 2eca3f1

tar -xa -C /image -f /data.tar.zst && \

This appears to fail on arm following this update, I suspect due to the old version of Docker we're using on our arm runners.

[brandond]

The issue appears to be something with the fchmodat2 function used by gnu tar; I seem to recall there being an issue with this ages ago but I'm having a hard time recalling exactly what it was.

symlinkat("coreutils", AT_FDCWD, "./bin/whoami") = -1 EEXIST (File exists)
unlinkat(AT_FDCWD, "./bin/whoami", 0)   = 0
symlinkat("coreutils", AT_FDCWD, "./bin/whoami") = 0
utimensat(AT_FDCWD, "./bin/whoami", [UTIME_OMIT, {tv_sec=1686773266, tv_nsec=25095773} /* 2023-06-14T20:07:46.025095773+0000 */], AT_SYMLINK_NOFOLLOW) = 0
fchownat(AT_FDCWD, "./bin/whoami", 0, 0, AT_SYMLINK_NOFOLLOW) = 0
fchmodat2(AT_FDCWD, "./bin/whoami", 0777, AT_SYMLINK_NOFOLLOW) = -1 EPERM (Operation not permitted)
fcntl64(1, F_GETFL)                     = 0x20002 (flags O_RDWR|O_LARGEFILE)
writev(2, [{iov_base="tar: ", iov_len=5}, {iov_base=NULL, iov_len=0}], 2tar: ) = 5
writev(2, [{iov_base="./bin/whoami: Cannot change mode"..., iov_len=45}, {iov_base=NULL, iov_len=0}], 2./bin/whoami: Cannot change mode to rwxrwxrwx) = 45
writev(2, [{iov_base=": Operation not permitted", iov_len=25}, {iov_base=NULL, iov_len=0}], 2: Operation not permitted) = 25

I think we can use busybox tar for this instead...

[brandond]

Related: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1972563.html

When using Docker in bookworm (current stable) and trying to run
containers based on newer distributions (like the recently released
Alpine 3.20), they will sometimes attempt to invoke newer syscalls like
fchmodat2. Due to the way syscalls that libseccomp does not know about
interact with Docker's seccomp profiles, these sometimes get EPERM
instead of ENOSYS like they should, which breaks their fallback.