Skip to content

fly hijack with -b displays container that does not match build ID specified #264

@kavinderd

Description

@kavinderd

When we tried to hijack a specific build, fly offered us the container from a different build. I believe we'd previously hijacked that older container, which is why it was still around.

screen shot 2016-01-20 at 4 00 44 pm

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions