You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I contributed some code to stepchowfun/docuum to use Bollard instead of invoking the Docker CLI, and almost immediately after releasing this version it was discovered that Bollard cannot parse the output of /system/df when if the user has been using BuildKit (stepchowfun/docuum#78).
Bollard is following exactly the Docker documentation, which was apparently wrong in this case (moby/moby#41264). The documentation was fixed in moby/moby#41267, but possibly the URL where Bollard pulls the API specifications from won't be updated until Docker 20.03 ships (I just checked and it hadn't been), and even then Bollard will need a rebuild because the generated code is in codegen/target/generated-sources/src/models.rs.
I don't know if you want to pick up the new spec from the repo now or if you want to wait until the spec is updated on the website. In the mean time, Docuum has gone back to using Docker CLI.
The text was updated successfully, but these errors were encountered:
Thanks for the detailed write-up and reporting this upstream.
I'm not against referencing the swagger YAML in a tag of moby's Github instead of the website, and regenerating the API stubs, though I'd want the tag somehow reflected in the versioning of the bollard-stubs repository. Perhaps, that could be done using an alpha release.
mdonoughe
pushed a commit
to mdonoughe/bollard
that referenced
this issue
Jul 29, 2020
I contributed some code to stepchowfun/docuum to use Bollard instead of invoking the Docker CLI, and almost immediately after releasing this version it was discovered that Bollard cannot parse the output of /system/df when if the user has been using BuildKit (stepchowfun/docuum#78).
Bollard is following exactly the Docker documentation, which was apparently wrong in this case (moby/moby#41264). The documentation was fixed in moby/moby#41267, but possibly the URL where Bollard pulls the API specifications from won't be updated until Docker 20.03 ships (I just checked and it hadn't been), and even then Bollard will need a rebuild because the generated code is in codegen/target/generated-sources/src/models.rs.
I don't know if you want to pick up the new spec from the repo now or if you want to wait until the spec is updated on the website. In the mean time, Docuum has gone back to using Docker CLI.
The text was updated successfully, but these errors were encountered: