Added a deserializer to BoundHostVolumes#63
Closed
djs98052 wants to merge 1 commit into
Closed
Conversation
Collaborator
|
Closed as project moved to https://github.com/docker-java/docker-java. Please check if that issue still persist and reissue there if necessary. |
kenshin54
pushed a commit
to dianping/docker-java
that referenced
this pull request
Oct 28, 2014
Bind.parse() fails when access mode is specified
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While using docker-java with docker client API v1.11, I was getting errors about processing the Volumes item in the container config. I added a deserializer to BoundHostVolumes that will simply ignore the contents and allow the parser to continue with the rest of the stream.
My original attempt was to parse the object, but since I was unfamiliar with the schema and also unfamiliar with the JsonParser. I have left that attempt in the comments for anyone who would like to pursue it further.
(#43)