Skip to content

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

Closed

Description

@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.

Activity

  1. changed the title [-]OCI build fails with `tar: Cannot open: Invalid argument`[/-] [+]OCI build fails on linux/arm64 with `tar: Cannot open: Invalid argument`[/+] on Jan 27, 2026
  2. changed the title [-]OCI build fails on linux/arm64 with `tar: Cannot open: Invalid argument`[/-] [+]OCI build on linux/arm64 started failing on Jan 14 with `tar: Cannot open: Invalid argument`[/+] on Jan 27, 2026
  3. changed the title [-]OCI build on linux/arm64 started failing on Jan 14 with `tar: Cannot open: Invalid argument`[/-] [+]OCI build on linux/arm64 started failing on Jan 14 with `tar: Cannot {mkdir,open}: Invalid argument`[/+] on Jan 27, 2026
  4. amotl commented on Jan 27, 2026

    @amotl
    ContributorAuthor

    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.

  5. amotl commented on Jan 28, 2026

    @amotl
    ContributorAuthor

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

  6. amotl commented on Jan 29, 2026

    @amotl
    ContributorAuthor

    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

  7. mfussenegger commented on Feb 2, 2026

    @mfussenegger
    Member

    Fixed with #258

  8. amotl commented on Feb 3, 2026

    @amotl
    ContributorAuthor

    Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions