Skip to content
This repository was archived by the owner on Jan 15, 2025. It is now read-only.
This repository was archived by the owner on Jan 15, 2025. It is now read-only.

--previous-build-manifest with different layer num causes panic #624

@antheas

Description

@antheas

If the user provides a --previous-build-manifest to rpm-ostree compose container-encapsulate which has a different number of max-layers than what was requested, the following line panics:

assert!(modified_build.len() <= bin_size.get() as usize);

Expected behavior would be to attempt to do the merge gracefully as far as this library is concerned. Failing that, rpm-ostree should emit a warning and ignore the previous manifest.

Context: I did a build that went from 100 layers to 50.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions