Skip to content

fix: add -J flag to tar for xz extraction in SDE Dockerfiles#3292

Open
dougch wants to merge 2 commits into
aws:mainfrom
dougch:fix/docker-tar-xz-flag
Open

fix: add -J flag to tar for xz extraction in SDE Dockerfiles#3292
dougch wants to merge 2 commits into
aws:mainfrom
dougch:fix/docker-tar-xz-flag

Conversation

@dougch

@dougch dougch commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Issues:

Resolves: n/a

Description of changes:

The SDE Dockerfiles extract a .tar.xz archive using tar -xf, which relies on tar auto-detecting xz compression. On Amazon Linux 2, tar does not support auto-detection for xz — it requires the explicit -J flag.

Sample Failure

#21 0.222 + tar -xf sde-external-9.44.0-2024-08-22-lin.tar.xz
#21 0.230 tar: This does not look like a tar archive
#21 0.234 xz: (stdin): File format not recognized

Fix: tar -xftar -xJf

Call-outs:

This will not run in PR CI — it only triggers on the image-build workflow.
It is unclear how long this has been broken — a version bump may introduce collateral failures.

Testing:

None — man tar confirms -J is the correct flag for xz decompression.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.

tar on Amazon Linux 2 may not auto-detect xz compression.
Explicitly pass -J to ensure .tar.xz extraction works.
@dougch dougch marked this pull request as ready for review June 8, 2026 18:31
@dougch dougch requested a review from a team as a code owner June 8, 2026 18:31
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@dougch dougch temporarily deployed to auto-approve June 8, 2026 18:32 — with GitHub Actions Inactive
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.17%. Comparing base (7f7d548) to head (2604338).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3292   +/-   ##
=======================================
  Coverage   78.17%   78.17%           
=======================================
  Files         689      689           
  Lines      123732   123732           
  Branches    17199    17199           
=======================================
+ Hits        96723    96725    +2     
  Misses      26089    26089           
+ Partials      920      918    -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

# This emulator is needed when running BoringSSL/AWS-LC code under Intel's SDE for each supported chip (like ice lake).
# https://software.intel.com/content/www/us/en/develop/articles/intel-software-development-emulator.html#system-configuration
wget ${SDE_MIRROR_URL} && tar -xf "${SDE_VERSION_TAG}.tar.xz" && rm "${SDE_VERSION_TAG}.tar.xz" && \
wget ${SDE_MIRROR_URL} && tar -xJf "${SDE_VERSION_TAG}.tar.xz" && rm "${SDE_VERSION_TAG}.tar.xz" && \

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

huh... does this mean our AL2 image builds have been broken for a while and we haven't noticed?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants