OCI build on linux/arm64 started failing on Jan 14 with `tar: Cannot {mkdir,open}: Invalid argument`

[amotl]

About

The CI workflow CrateDB Docker images test started failing on Jan 14, 11:02 AM GMT+1 with run 20990091330.

Details

The build log on ARM is flooded with tons of log messages like those.

#8 12.95 tar: jdk/lib/jfr: Cannot mkdir: Invalid argument
#8 12.95 tar: jdk/lib/server: Cannot mkdir: Invalid argument
#8 12.95 tar: jdk/lib/security: Cannot mkdir: Invalid argument

#8 12.95 tar: jdk/include/classfile_constants.h: Cannot open: Invalid argument
#8 12.95 tar: jdk/release: Cannot open: Invalid argument

Origin

That's the relevant update.

Updated Dockerfile to use CrateDB version 6.2.0.
CrateDB Docker images test #517: Commit 7a6f828 pushed by crate-jenkins

Evaluation

This error currently blocks evaluations of any other patch, and probably an upcoming release.

• Maintenance: Update to Python 3.12 on CI/GHA #251
• Maintenance: Update dependencies 2026-01 #252
• Maintenance: Update to psycopg2 2.9.11 #253
• Tests: Stop verifying for +DisableExplicitGC existence in options #254

[amotl]

Similarly like @BaurzhanSakhariev is investigating at #256 (comment) why we didn't see the other issue earlier, we may want to check why this signal (Jenkins commit failing CI) on Jan 14 did not receive any attention.

[amotl]

We submitted a patch to invoke existing C/GHA jobs each night.

• CI: Run jobs on schedule each night to protect against regressions #257

[amotl]

A recent CI run on a PR reveals the problem still exists, even after @mfussenegger tried to fix things?

https://github.com/crate/docker-crate/actions/runs/21479364233/job/61871423674?pr=257

[mfussenegger]

Fixed with #258

[amotl]

Thank you!