Skip to content

bug: cargo having issues with building image build-boot-artifacts-x86-host-sa #2941

Description

@manjeetbhati

Version

main

Describe the bug.

make images worked
but when I run make images-all or run cargo make --cwd pxe --env SA_ENABLEMENT=1 build-boot-artifacts-x86-host-sa, I see below errors.

2 warnings found (use docker --debug to expand):

  • InvalidDefaultArgInFrom: Default value for ARG $CONTAINER_RUNTIME_X86_64 results in empty or invalid base image name (line 19)
  • JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 26)
cargo make --cwd pxe --env SA_ENABLEMENT=1 build-boot-artifacts-x86-host-sa
[cargo-make] INFO - cargo make 0.37.24
[cargo-make] ERROR - Error while evaluating script for env: REPO_ROOT, exit code: 1
Script:
[
    "dirname $(cargo locate-project --message-format plain --workspace)",
]
Stdout:

Stderr:
error: failed to load manifest for workspace member `/home/manjeets/gb300/infra-controller/crates/admin-cli`

Caused by:
  failed to load manifest for dependency `carbide-api-model`

Caused by:
  failed to parse manifest at `/home/manjeets/gb300/infra-controller/crates/api-model/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.75.0).
  Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
dirname: missing operand
Try 'dirname --help' for more information.

[cargo-make] WARN - Build Failed.
make: *** [Makefile:126: images-boot-artifacts] Error 1

Any idea how to fix it?

Minimum reproducible example

cargo make --cwd pxe --env SA_ENABLEMENT=1 build-boot-artifacts-x86-host-sa

Relevant log output

Other/Misc.

No response

Code of Conduct

  • I agree to follow NVIDIA Infra Controller's Code of Conduct
  • I have searched the open bugs and have found no duplicates for this bug report

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugA defect in existing software (deprecated - use issue type, but it's needed for reporting now)

    Type

    No fields configured for Bug.

    Projects

    Status
    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions