Skip to content

up --frozen-lockfile doesn't fail when lockfile is outdated #1273

Description

@s-h-a-d-o-w

npx @devcontainers/cli up --help says:

  --frozen-lockfile                 Ensure lockfile exists and remains unchanged;
                                     fail otherwise.   [boolean] [default: false]

I just ran up --frozen-lockfile twice, changing devcontainer.json (Really simple - image and feature. Changed feature from one to another.) in between without updating the lockfile. Got success and the same container id both times.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions