Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

waitContainerCmd is useless when container has autoRemove or is short lived  #2356

Copy link
Copy link
Open
@bitstrings

Description

@bitstrings
Issue body actions

Because we can not change the condition of wait (https://docs.docker.com/reference/api/engine/version/v1.43/#tag/Container/operation/ContainerWait), if the container is destroyed before wait can be used, then we have no way to get the status code.

Also, the fact that we need to exec waitContainerCmd after the container start, is weird.

In my case, I have overridden the WaitContainerCmdExec class so the condition to be next-exit for my use case. With this, I am able to start waiting before starting the container and therefore get the status code.

I recommend having a way to set the condition on wait container.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.