aws / aws/aws-nitro-enclaves-cli

Nitro-cli 1.4.2 can not build encalve with linuxkit 1.5.2

Open
#723 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
156
Forks
99
PR merge metrics
No merged PRs in 30d

Description

# 准备 bug 报告信息
cat > bug-report.txt << EOF
Title: nitro-cli 1.4.2 incompatible with linuxkit v1.5.2 - "Unknown format type kernel+initrd-nogz"

Environment:
- Nitro CLI Version: 1.4.2
- Linuxkit Version: v1.5.2
- OS: $(cat /etc/os-release | grep PRETTY_NAME)
- Kernel: $(uname -r)

Error:
Linuxkit reported an error while creating the bootstrap ramfs:
"Error: error parsing formats: Unknown format type kernel+initrd-nogz"

Steps to reproduce:
1. Install nitro-cli 1.4.2
2. Build any Docker image
3. Run: nitro-cli build-enclave --docker-uri --output-file test.eif
4. Error occurs

Expected: Build should complete successfully
Actual: Build fails with "Unknown format type kernel+initrd-nogz"
EOF

Building Nitro Enclave...
Start building the Enclave Image...
Using the locally available Docker image...
Linuxkit reported an error while creating the bootstrap ramfs: "Error: Error parsing formats: Unknown format type kernel+initrd-nogz\n2025/11/10 16:37:13 error during command execution: Error parsing formats: Unknown format type kernel+initrd-nogz\n"
[ E48 ] EIF building error. Such error appears when trying to build an EIF file. In this case, the error backtrace provides detailed information on the failure reason.

For more details, please visit https://docs.aws.amazon.com/enclaves/latest/user/cli-errors.html#E48

If you open a support ticket, please provide the error log found at "/var/log/nitro_enclaves/err2025-11-10T08:37:13.494501125+00:00.log"

cat /var/log/nitro_enclaves/err2025-11-10T08:37:13.494501125+00:00.log
Action: Build Enclave
Subactions:
Failed to build enclave
Failed to build EIF from docker
Failed to create EIF image: LinuxkitExecError
Root error file: src/lib.rs
Root error line: 171

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with Nitro CLI 1.4.2, Linuxkit v1.5.2, and a Docker image, then inspect src/lib.rs around line 171 and the reported E48 log. Done means nitro-cli build-enclave completes successfully and no longer reports the unknown kernel+initrd-nogz format error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, rust
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.