Doug Tangren

this could just be a util you could to an `images.pull(opts).for_each(util::Progress)` or something similar

Docker daemons can know run builds in different modes https://docs.docker.com/develop/develop-images/build_enhancements/ Not sure if this affects the API. Let's investigate and see

Look into srcing info from api schema

3

https://github.com/docker/docker/blob/master/api/swagger.yaml

see https://github.com/bytecodealliance/wasmtime/pull/2434 We current have to work around some of these limitations by using a separate future executor that blocks for a lack of these interfaces in the past. Let's...

—watch sets the expectation that this project supports a workflow that doesn’t require manual restarts. You may find it useful to try and reload the config file itself changes.

It would be nice to separate the server bits from main and possibility normalize the common bits between the out of the box hyper server and the adapted rustls hyper...

The first attempt yields the feature but it could be done better with less string formatting Let's try a struct which implements Display instead to reduce string formatting

Rust users might be familiar with RUST_LOG env var but those new to rust might expect a verbose cli flag

Since splitting out the wasm mods into rust mods it became apparent the handler api needs some work.