Allow to send empty messages in StartContainerCmd by albers · Pull Request #111 · docker-java/docker-java

Skip to content

Navigation Menu

Sign in

Appearance settings

Conversation

This illustrates an issue with current docker-java: you cannot send a
StartContainerCmd without payload.
Any payload sent with the StartContainerCmd will cause the target
container to lose its customization.
So in order to just start a preconfigured container you must be able to
send an empty "{}" message to the /containers/{id}/start endpoint.

This is accomplished by all configuration defaulting to null in
combination with @JsonInclude(NON_EMPTY).

marcuslinke added a commit that referenced this pull request

Dec 11, 2014
Allow to send empty messages in StartContainerCmd

@albers albers deleted the empty-start-command branch

December 11, 2014 19:25