Open paolino opened 2 years ago
Hi @paolino. If you want to fix this, you probably need to modify the FromJSON
instance for ContainerConfig
to parse a null "Cmd"
as []
. For "StopSignal"
, I'm not sure what should be returned if the key isn't provided. Maybe SIGTERM
since the API says that's the default.
Can you create a test case for the JSON response you're seeing?
Hi, I changed almost all [x] to a newtype to support 'null' encoding. It's quite an invasive change because it was detecting this all over the ContainerConfig encoding. I have 100 containers in production which slowly made me fix the [x] . But I haven't checked the API docs. Sadly I messed up the indentation and hlint things so a PR is not ready. Btw you can have a look here and if you think it's something useful I can try o port it back to the original style. In that case, I need to know which indenter should I use :-)
hello I get 2 errors inspecting containers
[WARN] DockerClientDecodeError "Error in $.Config.Cmd: parsing [] failed, expected Array, but encountered Null"
[WARN] DockerClientDecodeError "Error in $.Config: key \"StopSignal\" not found"
where should I look to fix them? any hint very appreciated