FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

loadImageFromTar fails on 1.24 · Issue #670 · docker-java/docker-java · GitHub

  1. docker-java
  2. docker-java

Repository navigation

loadImageFromTar fails on 1.24 #670

New issue
New issue
Closed
Closed
loadImageFromTar fails on 1.24#670
Labels
transport/nettytype/bug
Milestone
3.0.6

Description

KostyaSha
opened on Aug 17, 2016
23:11:11.936 INFO  c.g.d.c.AbstractDockerClientTest - ################################## STARTING loadImageFromTar ##################################
23:11:12.103 ERROR c.g.d.c.async.ResultCallbackTemplate - Error during callback
io.netty.handler.codec.CorruptedFrameException: invalid JSON received at byte position 0: 4c6f6164656420696d6167653a20646f636b65722d6a6176612f6c6f61643a312e300a
    at io.netty.handler.codec.json.JsonObjectDecoder.decode(JsonObjectDecoder.java:163)
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:411)
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
    at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:72)
    at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:33)
    at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
    at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
    at io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:233)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
    at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:435)
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
    at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:250)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:123)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:571)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:512)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:426)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:398)
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:877)
    at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
    at java.lang.Thread.run(Thread.java:745)
23:11:12.185 INFO  c.g.d.c.AbstractDockerClientTest - ################################## END OF  ##################################

@leonsabr let's try identify it separately from #664

Activity

  1. KostyaSha
    added
    type/bug
    transport/netty
    API/1.24
    on Aug 17, 2016

  2. KostyaSha commented on Aug 17, 2016

    KostyaSha
    on Aug 17, 2016
    MemberAuthor

    @netty @normanmaurer maybe you can help how faster check/fix such issue?

  3. KostyaSha commented on Aug 18, 2016

    KostyaSha
    on Aug 18, 2016
    MemberAuthor

    Sorry, found. That docker returns text instead JSON!

     +-------------------------------------------------+
 |  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f |
+--------+-------------------------------------------------+----------------+
|00000000| 4c 6f 61 64 65 64 20 69 6d 61 67 65 3a 20 64 6f |Loaded image: do|
|00000010| 63 6b 65 72 2d 6a 61 76 61 2f 6c 6f 61 64 3a 31 |cker-java/load:1|
|00000020| 2e 30 0a                                        |.0.             |
+--------+-------------------------------------------------+----------------+

  4. KostyaSha commented on Aug 21, 2016

    KostyaSha
    on Aug 21, 2016
    MemberAuthor

    moby/moby#25557

  5. KostyaSha commented on Aug 21, 2016

    KostyaSha
    on Aug 21, 2016
    MemberAuthor

    Netty with Void call tries parse body and fails, that's bug

  6. KostyaSha commented on Aug 21, 2016

    KostyaSha
    on Aug 21, 2016
    MemberAuthor

    Appeared only at 1.24 because they added text response instead of empty body

  7. KostyaSha commented on Aug 25, 2016

    KostyaSha
    on Aug 25, 2016
    MemberAuthor

    @tejksat maybe you know how to fix? Void shouldn't try parse response body and be happy with returned 200 code.

  8. tejksat
    added a commit that references this issue on Aug 25, 2016

    Fix for docker-java#670

    3b154a9

  9. tejksat commented on Aug 25, 2016

    tejksat
    on Aug 25, 2016
    Contributor

    @KostyaSha PR #680

  10. KostyaSha commented on Aug 25, 2016

    KostyaSha
    on Aug 25, 2016
    MemberAuthor

    Cool! Thanks!

  11. tejksat
    added 3 commits that reference this issue on Aug 27, 2016

    Fix for docker-java#670

    548b247

    Fix for docker-java#670

    cc8dbea

    Fix for docker-java#670

    27bffd6
  12. KostyaSha
    added a commit that references this issue on Aug 28, 2016

    Fix for #670 (#680)

    c8ab23f
  13. KostyaSha
    added this to the 3.0.6 milestone on Aug 28, 2016

  14. KostyaSha commented on Aug 28, 2016

    KostyaSha
    on Aug 28, 2016
    MemberAuthor

    Fixed via #680

  15. KostyaSha
    closed this as completedon Aug 28, 2016
  16. panuse
    added a commit that references this issue on Aug 20, 2017

    Fix for docker-java#670 (docker-java#680)

    64574ba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    transport/nettytype/bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      Back | FazBrowse Home | New Git URL