-
Notifications
You must be signed in to change notification settings - Fork 549
inspectContainer fails because of large ExitCode #1052
Comments
I was surprised by this exit code value, since I'm used to shell values which are between 0 and 255 (if I remember correctly). So I investigated this. Turns out it is possible and is definitely a bug. First, I'll snip out the relevant potion of the stacktrace from the OP
So we know the error was caused by an Is that value even possible? Let's look at the types involved.
Since the max According to the Java language spec, |
@DavidHaunsch what OS are you running Docker on, and what OS runs inside your container? |
@johnflavin @mattnworb Thanks for your answer! |
updated CHANGELOG and bumped minor version. see #1052
Description
Lately I started a micrsoft/iis nanoserver. After stopping the container I wanted to get the state (including the exit code). But this request failed because the exit code is out of range of int.
How to reproduce
What do you expect
I expect to receive the ContainerState including a large ExitCode. To fix this, the ExitCode should be Long for instance instead of Integer.
What happened instead
dockerClient.inspectContainer(containerCreation.id()).state() failed with following exception:
Software:
docker version
: 18.06.0-cedocker API version
: 1.38The text was updated successfully, but these errors were encountered: