Anthony Emengo

Apologies, but it also hard for me to give a streamlined reproduction example. Our setup is trying make networking work through 2+ levels of nested containerization, which might be the...

Sorry for the long delay on this. I was able to reproduce with the a linuxkit built VM with the following yaml. ``` kernel: image: linuxkit/kernel:4.14.63 cmdline: "console=ttyS0 page_poison=1" init:...

Perhaps we could collapse the fields like docker does ```man $ docker run --help ... -u, --user string Username or UID (format: [:]) ... ```

@importhuman > any suggestions for source code The [samples](https://github.com/buildpacks/samples/tree/main/apps) repo is supposed be the go-to for this. Personally, I just use this super simple [go app](https://github.com/aemengo/hello) I made. > how...

@importhuman It's no problem at all! Thanks for giving it your best effort and keeping me in the loop.

Thanks for creating this issue! Is there a preferred user workflow that you have in mind for this? For instance, the user reads the `report.toml` via the supplied file argument?

Hey @SAY-droid427, I wanted to check on how you're finding this issue. In general, the way it works is that there's 2 code paths when building the application image: *...

@josegonzalez Agreed. This is an underlying premise with [pack-interact-mode](https://github.com/buildpacks/rfcs/pull/152).

@simonjjones @jromero @dfreilich Can we have a little more detail about what the original intent of `--dry-run` was? @haliliceylan and I were following the thread and are lost. In the...

So, the suggestion is that you can create a builder with a lifecycle specified as an image tag? specified just like you can with `pack build ... --lifecycle-image`? Or is...