Pedro Dias

The platform option is being passed to Docker as specified in https://docs.docker.com/engine/api/v1.41/#tag/Image/operation/ImageBuild I believe the issue is in Docker and in this case the only workaround is to pull it...

Interesting. But I don't see an easy fix for this one. Checking the container's status will not help. We can't assume the container finished correctly after a very fast lifecycle,...

The opts object is passed to docker-modem (https://github.com/apocas/dockerode/blob/master/lib/docker.js#L32), so technically you could pass a stream docker-modem. What do you want to do with that stream inside docker-modem?

Interesting. My Windows voodoo is not strong enough to know this one :)

Could you give more details? Can't replicate this.

Just ran the tests against those versions, the only difference was that I used node v13.8.0. Everything worked fine. Could you provide an example?

Probably dockerode is also waiting for docker which went silent. There are a few endpoints that unfortunately fail silently upstream :/ Do you have a copy of the PortBindings you...

Interesting, will check this one.

I can't replicated this, there's even a test for this. https://github.com/apocas/docker-modem/blob/master/test/modem_test.js#L109 INPUT: ```js var opts = { "limit": 12, "filters": { "label": ["staging", "env=green"] }, "t": ["repo:latest", "repo:1.0.0"] }; ```...

Missed that. Can't remember why that was done. I suspect that endpoints didn't behave the same way, regarding input. Will check if removing the stringify doesn't break anything.